| 3 |
Approval of the Agenda |
|
| R3-250001 |
RAN3#127 Meeting Agenda |
RAN3 Chair |
| 4 |
Approval of the minutes from previous meetings |
|
| R3-250002 |
RAN3#126 Meeting Report |
ETSI-MCC |
| 5 |
Documents for immediate consideration |
|
| R3-250003 |
Guidelines for RAN3 Meetings |
RAN3 Chair, RAN3 Vice-Chairs |
| 7 |
General, protocol principles and issues |
|
| R3-250004 |
TR 30.531 v1.56.0 Work Plan and Working Procedures - RAN WG3 |
ETSI-MCC |
| R3-250756 |
TR 30.531 v1.56.0 Work Plan and Working Procedures - RAN WG3 |
ETSI-MCC |
| 8.1 |
New Incoming LSs |
|
| R3-250005 |
Reply LS on RAN3 vs RAN2 Basketball Match |
RAN2(Oppo) |
| R3-250006 |
LS on emergency services and eDRX |
RAN2(ZTE) |
| R3-250007 |
Reply LS to SA5 on AIML data collection |
RAN2(Nokia) |
| R3-250009 |
Reply LS to SA2 on AIML data collection |
RAN2(Interdigital) |
| R3-250012 |
LS on XR UL bit rate control |
RAN2(Meta) |
| R3-250013 |
LS on RAN2 outcome of Ambient IoT study |
RAN2(Huawei) |
| R3-250015 |
Reply LS on UAV regulation |
SA1(Huawei) |
| R3-250018 |
LS Reply on FS_XRM Ph2 |
SA2(Huawei) |
| R3-250022 |
Reply LS on UAV regulation |
SA2(Samsung) |
| R3-250025 |
LS on A-IoT Conclusions in SA WG2 |
SA2(Huawei) |
| R3-250027 |
LS Reply on multi-modality awareness |
SA4(Huawei) |
| R3-250029 |
Reply LS on MDT configuration control in NR-DC |
SA5(Ericsson) |
| R3-250032 |
LS on multi-modality awareness |
TSG SA(China mobile) |
| R3-250057 |
Further LS on Assistance information from CN to the reader |
RAN2(ZTE) |
| R3-250069 |
Reply LS on Assistance Information from CN to the Reader |
SA2(ZTE) |
| R3-250075 |
LS on SA2 Ambient IoT TR conclusion update |
SA2(Huawei) |
| R3-250122 |
Discussion on SA2 Ambient IoT TR conclusion update |
ZTE Corporation |
| R3-250123 |
[DRAFT] Reply LS on SA2 Ambient IoT TR conclusion update |
ZTE Corporation |
| R3-250177 |
Discussion on MMSID-aware admission control and QoS flow to DRB mapping |
NEC |
| R3-250178 |
Support of MMSID-aware admission control and QoS flow to DRB mapping |
NEC |
| R3-250195 |
Consideration on SA2 Ambient IoT TR conclusion update |
Huawei, China Unicom |
| R3-250196 |
[Draft] Reply LS on SA2 Ambient IoT TR conclusion update |
Huawei |
| R3-250213 |
Discussion on the LS related to XR |
Nokia, Nokia Shanghai Bell |
| R3-250214 |
[DRAFT] Reply LS on XR UL bit rate control |
Nokia, Nokia Shanghai Bell |
| R3-250268 |
Discussion on LS on XR UL bit rate control |
Lenovo |
| R3-250292 |
Discussion on the XR UL bit rate control |
Huawei |
| R3-250293 |
[draft] Reply LS on XR UL bit rate control |
Huawei |
| R3-250294 |
Discussion on the XR available data rate report |
Huawei |
| R3-250295 |
[draft] Reply LS on FS_XRM Ph2 for available data rate report |
Huawei |
| R3-250332 |
Discussion on LS for XR |
CATT |
| R3-250370 |
Discussion on the reply LSs on UAV regulation from SA1 and SA2 |
Huawei |
| R3-250371 |
[Draft] Reply LS on UAV regulation |
Huawei |
| R3-250424 |
Discussion on UAV Regulation – Altitude Reporting |
CATT |
| R3-250425 |
UAV Regulation - Altitude Reporting (stage 2) |
CATT |
| R3-250426 |
Altitude Reporting for aerial UE-NG |
CATT |
| R3-250427 |
[draft] Reply LS on on UAV regulation |
CATT |
| R3-250442 |
On the LS from SA2 on Ambient IoT TR conclusion update (S2-2501343/R3-250075) |
Ericsson |
| R3-250443 |
[DRAFT] Reply LS on SA2 Ambient IoT TR conclusion update |
Ericsson |
| R3-250474 |
Discussion on RAN2 LS on XR UL bit rate control |
Ericsson |
| R3-250475 |
[Draft] Reply LS on XR UL bit rate control |
Ericsson |
| R3-250476 |
Discussion on SA2 LS on XR enhancements |
Ericsson |
| R3-250477 |
[Draft] Reply LS on Available Data Rate notion and impacts |
Ericsson |
| R3-250516 |
Reply LS on XR UL Bit Rate Control |
CMCC |
| R3-250517 |
Discussion on XR UL Bit Rate Control |
CMCC |
| R3-250518 |
Reply SA2 LS Reply on FS_XRM Ph2 Regarding Reporting Available Data Rate From RAN |
CMCC |
| R3-250519 |
Discussion on SA2 LS Reply on FS_XRM Ph2 Regarding Available Data Rate Reporting from RAN |
CMCC |
| R3-250520 |
Reply LS on Multi-Modality Awareness |
CMCC |
| R3-250521 |
Discussion on SA4 LS Reply on Multi-Modality Awareness |
CMCC |
| R3-250541 |
Support UAV UE Flight Information Reporting to CN |
Ericsson |
| R3-250544 |
Support UAV UE Flight Information Reporting to CN |
Ericsson |
| R3-250545 |
[Draft] Reply LS on UAV regulation |
Ericsson |
| R3-250546 |
Support UAV UE Flight Information Reporting to CN |
Ericsson |
| R3-250553 |
Emergency Services and INACTIVE eDRX |
Nokia |
| R3-250554 |
Correction of Emergency and inactive eDRX |
Nokia |
| R3-250555 |
Correction of Emergency and inactive eDRX |
Nokia |
| R3-250556 |
Reply LS on emergency services and eDRX |
Nokia |
| R3-250557 |
Analysis of AIoT Conclusions in SA WG2 |
Nokia |
| R3-250558 |
Reply LS on AIoT Conclusions in SA WG2 |
Nokia |
| R3-250559 |
Analysis of SA2 AIoT TR configuration aspects |
Nokia |
| R3-250560 |
TP on information exchange for feedback on SA2 AIoT TR |
Nokia |
| R3-250561 |
Reply LS on SA2 Ambient IoT TR Conclusion Update |
Nokia |
| R3-250600 |
Discussion on multi-modality awareness |
Huawei |
| R3-250601 |
[draft] Reply LS on multi-modality awareness |
Huawei |
| R3-250602 |
Correction to support multi-modality awareness |
Huawei |
| R3-250603 |
Correction to support multi-modality awareness |
Huawei |
| R3-250604 |
(TP for BL CR for TS 38.473) Support for multi-modality awareness |
Huawei |
| R3-250605 |
(TP for BL CR for TS 38.423) Support for multi-modality awareness |
Huawei |
| R3-250630 |
Discussion on LS for XR UL bit rate control |
Samsung |
| R3-250657 |
Consideration on A-IoT Conclusions in SA WG2 |
Huawei |
| R3-250658 |
[Draft] Reply LS on A-IoT Conclusions in SA WG2 |
Huawei |
| R3-250659 |
(TP for TS 38.415) XR available data rate report |
Huawei |
| R3-250660 |
(TP for TS 38.413) XR available data rate report |
Huawei |
| R3-250691 |
Discussion on UAV information reporting |
CMCC |
| R3-250692 |
Correction to support UAV information reporting |
CMCC |
| R3-250693 |
Discussion on the emergency services and eDRX |
Huawei |
| R3-250694 |
Emergency services and eDRX for RRC inactive UE |
Huawei |
| R3-250695 |
Emergency services and eDRX for RRC inactive UE |
Huawei |
| R3-250698 |
Discussion on XR UL Rate Control |
Meta |
| R3-250699 |
Draft Reply LS on XR UL Rate Control |
Meta |
| R3-250706 |
Correction on altitude information reporting for aerial UE |
ZTE Corporation |
| R3-250707 |
Correction on altitude information reporting for aerial UE |
ZTE Corporation, |
| R3-250708 |
Correction on altitude information reporting for aerial UE |
ZTE Corporation, |
| R3-250709 |
[draft] Reply LS on on UAV regulation |
ZTE Corporation |
| R3-250710 |
Further discussion on UAV regulation based on reply LS |
ZTE Corporation |
| R3-250711 |
Discussion on XR UL bit rate control |
ZTE Corporation |
| R3-250712 |
[DRAFT] Reply LS on XR UL bit rate control |
ZTE Corporation |
| R3-250713 |
Correction on XR UL bit rate control |
ZTE Corporation |
| R3-250714 |
Correction on available data rate |
ZTE Corporation |
| R3-250715 |
[DRAFT]Response LS to SA2 on FS_XRM Ph2 |
ZTE Corporation |
| R3-250716 |
Further discussion on the available data rate |
ZTE Corporation |
| R3-250717 |
Discussion on multi-modality based on received LS |
ZTE Corporation |
| R3-250746 |
Response to R3-250693 and R3-250553 |
ZTE Corporation |
| R3-250748 |
Response to R3-250553 and R3-250693 |
Ericsson |
| R3-250758 |
CB:#1_UAVInforReport |
CMCC |
| R3-250798 |
Reply LS on XR UL bit rate control |
RAN3(Meta) |
| R3-250799 |
Reply LS on FS_XRM Ph2 for available data rate report |
RAN3(Huawei) |
| R3-250805 |
Reply LS on XR UL Rate Control |
RAN3(Meta) |
| R3-250806 |
Reply LS on FS_XRM Ph2 for available data rate report |
RAN3(Huawei) |
| R3-250865 |
LS on UAV regulation from RAN3 |
RAN3(CMCC) |
| R3-250866 |
Correction on altitude information reporting for aerial UE |
CATT |
| R3-250867 |
Correction on altitude information reporting for aerial UE |
Ericsson |
| R3-250868 |
Correction on altitude information reporting for aerial UE |
ZTE |
| R3-250876 |
LS on UAV regulation from RAN3 |
RAN3(CMCC) |
| 8.2 |
LSin received during the meeting |
|
| R3-250793 |
Reply to LS on Application-Layer FEC Awareness at RAN |
SA4(Qualcomm) |
| R3-250809 |
Reply LS to SA2 |
RAN2(vivo) |
| R3-250836 |
Reply on PDCP SN gap report handling during UE mobility |
RAN2(Huawei) |
| 8.3 |
Left over LSs / pending actions |
|
| R3-250026 |
LS Reply on MBS Communication Service Type |
SA4(Huawei) |
| R3-250508 |
MBS Communication Service Type for QMC |
Ericsson |
| R3-250509 |
(CR TS 38.413) MBS Communication Service Type for QMC |
Ericsson |
| R3-250510 |
(CR TS 38.423) MBS Communication Service Type for QMC |
Ericsson |
| R3-250654 |
Clarification on MBS communication service type for QMC configuration |
Huawei |
| R3-250655 |
Clarification on MBS communication service type for QMC configuration |
Huawei |
| R3-250656 |
[Draft] Reply LS to S4-242151 on MBS Communication Service Type |
Huawei |
| R3-250739 |
MBS Communication Service Type for QMC |
Ericsson |
| R3-250740 |
MBS Communication Service Type for MBS |
Ericsson |
| R3-250741 |
MBS Communication Service Type for MBS |
Ericsson |
| R3-250742 |
MBS Communication Service Type for QMC |
Ericsson |
| R3-250743 |
(CR TS 38.413) MBS Communication Service Type for QMC |
Ericsson |
| R3-250744 |
(CR TS 38.423) MBS Communication Service Type for QMC |
Ericsson |
| R3-250751 |
Response to R3-250739 and R3-250656 |
ZTE Corporation |
| R3-250754 |
Response to R3-250739 |
Huawei Telecommunication India |
| R3-250858 |
Reply LS on MBS Communication Service Type |
RAN3(ZTE) |
| 9.1 |
LTE |
|
| R3-250017 |
Reply LS on UE Location Information for NB-IoT NTN |
SA2(Qualcomm) |
| R3-250215 |
Discussion on the UE Location Information for NB-IoT NTN |
Nokia, Nokia Shanghai Bell |
| R3-250216 |
[DRAFT] Reply LS on UE Location Information for NB-IoT NTN |
Nokia, Nokia Shanghai Bell |
| R3-250237 |
Discussion on Coarse UE Location Information for NB-IoT UEs |
Qualcomm Incorporated |
| R3-250305 |
Some Clarifications on UE Location Information for IoT NTN |
Ericsson, Thales, Viasat, Inmarsat, Huawei, ESA |
| R3-250406 |
Further discussion on UE Location Information for NB-IoT NTN |
Huawei, Ericsson |
| R3-250418 |
Coarse UE location information transfer for NB-IoT NTN-X2 |
CATT, CMCC, ZTE, Qualcomm |
| R3-250496 |
Discussion on coarse UE location information transfer for NB-IoT NTN |
ZTE Corporation, CMCC, CATT |
| R3-250497 |
[DRAFT] Reply LS on UE Location Information for NB-IoT NTN |
ZTE Corporation, CMCC, CATT |
| R3-250679 |
Stage2 correction for coarse UE location information transfer for NB-IoT NTN |
CMCC, CATT, ZTE |
| R3-250761 |
Reply LS on UE Location Information for NB-IoT NTN |
RAN3(Qualcomm) |
| 9.2 |
NR |
|
| R3-250010 |
LS on inter-gNB RACH-less HO in NTN |
RAN2(Nokia) |
| R3-250066 |
Correction on UE XnAP ID in IAB procedures |
ZTE Corporation, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-250067 |
Correction on UE XnAP ID in IAB procedures |
ZTE Corporation, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-250079 |
Clarification of the description of the UE History Information |
Nokia, ZTE, CMCC |
| R3-250080 |
Clarification on resumption of non-SDT bearer in SDT termination |
Google, ZTE, Nokia, CATT, LG Electronics, Ericsson, Lenovo |
| R3-250081 |
Clarification on PDU Session Management collision with handover or LTM |
Google |
| R3-250082 |
Clarification on UE Context Modification Failure for LTM |
Google |
| R3-250115 |
F1 support for L3 measurements-based LTM |
ZTE Corporation, Ericsson, CATT, Vodafone, Nokia, LG Electronics, Samsung |
| R3-250124 |
Clarification for propagation of MDT Configuration EUTRA |
Huawei, Nokia, Ericsson |
| R3-250131 |
Correction of N3IWF user location information |
Huawei, Nokia, Nokia ShanghaiBell, CATT |
| R3-250132 |
Correction of N3IWF user location information |
Huawei, Nokia, Nokia ShanghaiBell, CATT |
| R3-250135 |
Correction on criticality of SRS Reservation Type |
ZTE Corporation, CATT, Ericsson, Nokia, Huawei, CMCC, Qualcomm Incorporated, Samsung |
| R3-250136 |
Correction on criticality of SRS Reservation Type |
ZTE Corporation, CATT, Ericsson, Nokia, Huawei, CMCC, Qualcomm Incorporated, Samsung |
| R3-250137 |
Clarification on predicted UE trajectory over HO Request |
ZTE Corporation, Samsung, CMCC, China Unicom, China Telecom |
| R3-250138 |
Additional procedural text measured UE trajectory request |
ZTE Corporation, Ericsson, InterDigital, Jio Platforms |
| R3-250158 |
Correction on AMF Name |
Huawei, Nokia, NEC |
| R3-250204 |
Editorial correction on TNL Configuration Info |
NTTDOCOMO, INC. |
| R3-250205 |
Editorial correction on TNL Configuration Info |
NTTDOCOMO, INC. |
| R3-250217 |
Discussion on inter-gNB RACH-less HO in NTN |
Nokia, Nokia Shanghai Bell, Samsung, CATT, Thales, Huawei, Qualcomm, Vivo |
| R3-250218 |
[DRAFT] Reply LS on inter-gNB RACH-less HO in NTN |
Nokia, Nokia Shanghai Bell, Samsung, CATT, Thales, Huawei, Qualcomm, Vivo |
| R3-250249 |
Inclusion of C-RNTI for SHR |
Huawei, Qualcomm, BT |
| R3-250250 |
Inclusion of C-RNTI for SHR |
Huawei, Qualcomm, BT |
| R3-250251 |
Inclusion of C-RNTI for SHR |
Huawei, Qualcomm, BT |
| R3-250252 |
Inclusion of C-RNTI for SHR |
Huawei, Qualcomm, BT |
| R3-250253 |
Inclusion of C-RNTI for SHR |
Huawei, Qualcomm, BT |
| R3-250254 |
Inclusion of C-RNTI for SHR |
Huawei, Qualcomm, BT |
| R3-250260 |
Correction on the mobile IAB procedures |
Huawei, Lenovo, ZTE |
| R3-250261 |
Correction on the PDU set information |
Huawei, CMCC, Ericsson, CATT, Nokia, Nokia Shanghai Bell |
| R3-250264 |
Correction of a wrong description of the S-NG-RAN node Counter Check procedure |
Nokia |
| R3-250265 |
Correction of a wrong description of the S-NG-RAN node Counter Check procedure |
Nokia |
| R3-250266 |
Correction of a wrong description of the S-NG-RAN node Counter Check procedure |
Nokia |
| R3-250267 |
Correction of a wrong description of the S-NG-RAN node Counter Check procedure |
Nokia |
| R3-250301 |
Further discussion on L3 measurement based LTM |
Huawei, China Telecom, CMCC |
| R3-250302 |
Support of L3 measurement based LTM over F1 |
Huawei, China Telecom, CMCC |
| R3-250303 |
Support of L3 measurement based LTM over F1 |
Huawei, China Telecom, CMCC |
| R3-250304 |
Support of L3 measurement based LTM over F1 |
Huawei, China Telecom, CMCC |
| R3-250306 |
Supporting Inter-gNB RACH-less Handover |
Ericsson |
| R3-250321 |
Correction of TSC Traffic Characteristics |
Huawei, Nokia, China Telecom |
| R3-250322 |
Correction of TSC Traffic Characteristics |
Huawei, Nokia, China Telecom |
| R3-250323 |
Correction of TSC Traffic Characteristics |
Huawei, Nokia, China Telecom |
| R3-250324 |
Correction on LBT failure information |
CATT |
| R3-250355 |
(draft CR to F1AP) Discussion on L3 measurement report for SCell activation |
CATT, China Telecom, CMCC |
| R3-250383 |
Correction of Paging Policy Differentiation |
Huawei, Ericsson, China Unicom, China Telecom |
| R3-250384 |
Correction of Backup AMF Name |
Huawei, China Unicom, China Telecom, Vodafone |
| R3-250385 |
Correction of Backup AMF Name |
Huawei, China Unicom, China Telecom, Vodafone |
| R3-250386 |
Correction of Backup AMF Name |
Huawei, China Unicom, China Telecom, Vodafone |
| R3-250389 |
Discussion on Cell Information for UAV and ATG over Xn interface |
China Telecom |
| R3-250390 |
Correction on ATG Cell Information over Xn interface |
China Telecom, ZTE, China Unicom |
| R3-250391 |
Correction on UAV Cell Information over Xn interface |
China Telecom, ZTE, China Unicom |
| R3-250392 |
Correction on the support of MBS in QoS Flow Level QoS Parameters and QoS Flow Identifier |
China Telecom, ZTE, CATT, China Unicom |
| R3-250393 |
Correction on the support of MBS in QoS Flow Level QoS Parameters and QoS Flow Identifier |
China Telecom, ZTE, CATT, China Unicom |
| R3-250394 |
Correction on QoS Flow List and QoS Flow Identifier |
China Telecom, ZTE, China Unicom |
| R3-250396 |
Correction on QoS Flow List and QoS Flow Identifier |
China Telecom, ZTE , China Unicom |
| R3-250420 |
(Draft LS) Discuss about rach-ConfigCommon in Rel-18 LTM |
CATT |
| R3-250433 |
Correction of Emergency Services |
Nokia |
| R3-250448 |
Stage 2 correction for network slice support during XN handover |
Ericsson, Jio Platforms (JPL), AT&T, Rakuten, FiberCop, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia, Huawei, Samsung, ZTE |
| R3-250449 |
Discussion on multiple Xn Setup procedures |
Ericsson |
| R3-250450 |
Additional procedural text for data collection configuration |
Ericsson, ZTE Corporation, Jio Platforms (JPL), InterDigital |
| R3-250451 |
Discussion on Data Collection Reporting procedure’s interaction with Handover Request procedure |
Ericsson, Jio Platforms (JPL), InterDigital, FiberCop |
| R3-250452 |
Correction for Data Collection Reporting procedure's interaction with Handover Request procedure |
Ericsson, Jio Platforms (JPL), InterDigital, FiberCop |
| R3-250453 |
Discussion on packet loss as UE performance metric |
Ericsson, Jio Platforms (JPL), Deutsche Telekom |
| R3-250454 |
Correction to exclude Packet Loss as a UE Performance metric |
Ericsson, Jio Platforms (JPL), Deutsche Telekom |
| R3-250478 |
Correction on UE Radio Capability for Paging IE |
Ericsson, Qualcomm Inc., Vodafone |
| R3-250479 |
Correction on UE Radio Capability for Paging IE |
Ericsson, Qualcomm Inc., Vodafone |
| R3-250480 |
Correction on UE Radio Capability for Paging IE |
Ericsson, Qualcomm Inc., Vodafone |
| R3-250481 |
Correction on Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT |
| R3-250482 |
Correction on Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT |
| R3-250483 |
Correction on Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT |
| R3-250484 |
Correction on Positioning Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT |
| R3-250485 |
Correction on Positioning Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT |
| R3-250486 |
Correction on Positioning Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT |
| R3-250498 |
Clarification on neighbour information for EN-DC Configuration Update procedure |
ZTE Corporation, CATT, China Telecom, CMCC |
| R3-250524 |
Correction on handover failure due to unavailable candidate relay UE |
Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung |
| R3-250525 |
Correction on handover failure due to unavailable candidate relay UE |
Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung |
| R3-250542 |
Triggering LTM without L1 measurements UE capability |
Ericsson, CATT, ZTE, Lenovo, LG Electronics |
| R3-250543 |
F1 support for L3 measurements-based LTM |
Ericsson, Vodafone, CATT, ZTE, NTT DoCoMo, Nokia, Samsung, LG Electronics, Lenovo |
| R3-250563 |
Support of L3 measurement based LTM over F1 for DU based solution |
Qualcomm Inc, NTT DOCOMO, AT&T, Apple Inc, Rakuten, JIO Platforms |
| R3-250564 |
Support of L3 measurement based LTM over F1 for DU based solution (stage-3) |
Qualcomm Inc, NTT DOCOMO, AT&T, Apple Inc, Rakuten, JIO Platforms |
| R3-250565 |
Support of L3 measurement based LTM over F1 for DU based solution (stage-3) |
Qualcomm Inc, NTT DOCOMO, AT&T, Apple Inc, JIO Platforms, Rakuten |
| R3-250566 |
Stage-2 Support of L3 measurement based LTM for DU based solution |
Qualcomm Inc, NTT DOCOMO, AT&T, Apple Inc, JIO Platforms, Rakuten |
| R3-250568 |
Way forward Signaling enhancements to support L3 measurement based R18 LTM |
Qualcomm Inc, Apple Inc, AT&T, NTT DOCOMO, JIO Platforms, Rakuten, Tejas Networks, Boost Mobile Networks (USA), Fujitsu |
| R3-250584 |
Stage 2 updates for support of L3 measurements based LTM |
CATT, Ericsson, Vodafone, ZTE, Google, Samsung, LG Electronics, NTT DoCoMo, Nokia |
| R3-250588 |
Clarification on Paging Policy Indicator |
Huawei, China Unicom, China Telecom |
| R3-250589 |
Clarification on Paging Policy Indicator |
Huawei, China Unicom, China Telecom |
| R3-250590 |
Clarification on Paging Policy Indicator |
Huawei, China Unicom, China Telecom |
| R3-250591 |
Clarification on Paging Policy Indicator |
Huawei, China Unicom, China Telecom |
| R3-250614 |
Correction on reference in SCG failure information reporting |
Samsung |
| R3-250615 |
Correction on reference in SCG failure information reporting |
Samsung |
| R3-250631 |
Correction to SRS information |
Samsung, ZTE, CATT, Qualcomm, Nokia, China Telecom |
| R3-250632 |
Correction to SRS information |
Samsung, ZTE, CATT, Qualcomm, Nokia, China Telecom |
| R3-250639 |
Discussion on L3 measurement based LTM |
Samsung |
| R3-250644 |
Correction on PDU session-level indirect data forwarding [Indirect Data Forwarding] |
LG Electronics Inc., Huawei |
| R3-250668 |
Correction on UE radio capability for paging information |
CMCC, Huawei, CATT |
| R3-250669 |
Correction on UE radio capability for paging information |
CMCC, Huawei, CATT |
| R3-250670 |
Correction on UE radio capability for paging information |
CMCC, Huawei, CATT |
| R3-250677 |
[Draft] LS Reply on inter-gNB RACH-less HO in NTN |
CMCC |
| R3-250678 |
Stage2 Correction for AI/ML Terminology description |
CMCC, QUALCOMM, Huawei |
| R3-250690 |
Correction for name of AP ID over Xn interface |
CMCC, CATT, ZTE, Huawei, NEC, Nokia |
| R3-250726 |
Discussion on abnormal case of Xn setup procedure |
ZTE Corporation |
| R3-250727 |
Correction on Xn Setup message |
ZTE Corporation |
| R3-250728 |
Correction on Xn Setup message |
ZTE Corporation |
| R3-250729 |
Correction on Xn Setup message |
ZTE Corporation |
| R3-250730 |
Correction on Xn Setup message |
ZTE Corporation |
| R3-250731 |
DU based L3 measurement LTM |
Huawei, China Unicom |
| R3-250732 |
DU based L3 measurement LTM |
Huawei |
| R3-250762 |
Reply LS on inter-gNB RACH-less HO in NTN |
RAN3(Nokia) |
| R3-250763 |
draft LS to RAN2 on L3 measurements based LTM over F1 |
Vodafone |
| R3-250764 |
Correction on Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT, ZTE, China Telecom |
| R3-250765 |
Correction on Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT, ZTE, China Telecom |
| R3-250766 |
Correction on Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT, ZTE, China Telecom |
| R3-250767 |
Correction on Positioning Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT, ZTE, China Telecom |
| R3-250768 |
Correction on Positioning Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT, ZTE, China Telecom |
| R3-250769 |
Correction on Positioning Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT, ZTE, China Telecom |
| R3-250770 |
Clarification of the description of the UE History Information |
Nokia, ZTE, CMCC |
| R3-250771 |
Clarification on predicted UE trajectory over HO Request |
ZTE Corporation, Samsung, CMCC, China Unicom, China Telecom |
| R3-250772 |
Clarification on resumption of non-SDT bearer in SDT termination |
Google, ZTE, Nokia, CATT, LG Electronics, Ericsson, Lenovo, Huawei |
| R3-250773 |
Stage 2 correction for network slice support during XN handover |
Ericsson, Jio Platforms (JPL), AT&T, Rakuten, FiberCop, InterDigital, Deutsche Telekom, NTT DoCoMo, Nokia, Huawei, Samsung, ZTE, CMCC |
| R3-250774 |
Correction on the support of MBS in QoS Flow Level QoS Parameters and QoS Flow Identifier |
China Telecom, ZTE, CATT, China Unicom, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-250775 |
Correction on the support of MBS in QoS Flow Level QoS Parameters and QoS Flow Identifier |
China Telecom, ZTE, CATT, China Unicom, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-250776 |
Correction on QoS Flow List and QoS Flow Identifier |
China Telecom, ZTE, China Unicom, CATT, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-250777 |
Correction on QoS Flow List and QoS Flow Identifier |
China Telecom, ZTE, China Unicom, CATT, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-250778 |
Correction on the PDU set information |
Huawei, CMCC, Ericsson, CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-250779 |
Correction of Paging Policy Differentiation |
Huawei, Ericsson, China Unicom, China Telecom, Nokia, ZTE |
| R3-250780 |
Correction on UE XnAP ID in IAB procedures |
ZTE Corporation, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R3-250781 |
Correction on UE XnAP ID in IAB procedures |
ZTE Corporation, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R3-250811 |
Clarification on UE Context Modification Failure for LTM |
Google, Huawei, Nokia, Ericsson, LG Electronics, Samsung, ZTE, CATT, NEC, China Telecom |
| R3-250847 |
Correction on LBT failure information |
CATT |
| R3-250848 |
Clarification for propagation of MDT Configuration EUTRA |
Huawei, Nokia, Ericsson |
| R3-250857 |
Stage 2 correction on DL LBT failure information |
Ericsson, Nokia |
| R3-250860 |
[draft] LS about LTM CSC MAC CE with CFRA |
RAN3(CATT) |
| R3-250872 |
Correction for Data Collection Reporting procedure's interaction with Handover Request procedure |
Ericsson, Jio Platforms (JPL), InterDigital, FiberCop, Huawei, Lenovo, ZTE, Samsung, Nokia |
| R3-250879 |
Reply LS on L3 measurement based LTM support over F1 |
RAN3(Vodafone) |
| R3-250880 |
Clarification for propagation of MDT Configuration EUTRA |
Huawei, Nokia, Ericsson, ZTE, Samsung |
| R3-250881 |
Correction on DL LBT failure information |
CATT, Ericsson, Nokia, Huawei, ZTE |
| R3-250882 |
Stage 2 correction on DL LBT failure information |
Ericsson, Nokia |
| R3-250883 |
Correction for Data Collection Reporting procedure's interaction with Handover Request procedure |
Ericsson, Jio Platforms (JPL), InterDigital, FiberCop, Huawei, Lenovo, ZTE, Samsung, Nokia |
| R3-250886 |
Correction of a wrong description of the S-NG-RAN node Counter Check procedure |
Nokia |
| R3-250887 |
Correction on handover failure due to unavailable candidate relay UE |
Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, Samsung, ZTE, Huawei |
| R3-250916 |
Correction on Assistance Information Control Procedure |
Ericsson, Nokia, Qualcomm Inc., Huawei, CATT, ZTE, China Telecom |
| R3-250917 |
Correction on QoS Flow List and QoS Flow Identifier |
China Telecom, ZTE, China Unicom, CATT, Nokia, Nokia Shanghai Bell, Huawei, Samsung |
| R3-250918 |
Correction on UE XnAP ID in IAB procedures |
ZTE Corporation, Huawei, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| 10.1 |
General |
|
| R3-250033 |
(BL CR to 36.300 for SON) Addition of SON enhancements |
Lenovo |
| R3-250034 |
(BL CR to 36.423) Addition of SON enhancements |
CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia |
| R3-250035 |
(BL CR to 37.340 for SON) on MRO for S-CPAC |
CMCC |
| R3-250036 |
(BL CR to 38.413 for MDT) Addition of MDT enhancements |
Nokia |
| R3-250037 |
(BL CR to 38.423 for MDT) Addition of MDT enhancements |
CATT |
| R3-250038 |
(BL CR to 38.423 for SON) Addition of SON enhancements |
ZTE Corporation, Samsung, Nokia, Lenovo, Jio |
| R3-250039 |
(BL CR to 38.473 for SON) Addition of SON enhancements |
Huawei, Nokia, Jio |
| R3-250040 |
(BL CR to 38.300 for SON) Addition of SON enhancements |
China Unicom, Nokia, Huawei, Lenovo, CATT, Ericsson, Qualcomm Inc., Samsung, LG Electronics Inc, ZTE Corporation |
| R3-250041 |
(BL CR to 38.401 for SON) Addition of SON enhancements |
ZTE Corporation, Nokia, Huawei, Lenovo, CATT, Ericsson, Samsung |
| R3-250733 |
Workplan for Rel-19 SON_MDT Enhancement |
China Unicom, CMCC |
| R3-250926 |
(BL CR to 36.423 for SON) Addition of SON enhancements |
CATT, Samsung, Lenovo, Huawei, Ericsson, ZTE, CMCC, Nokia, Jio Platforms |
| R3-250927 |
(BL CR to 37.340 for SON) on MRO for S-CPAC |
CMCC |
| R3-250928 |
(BL CR to 38.300 for SON) Addition of SON enhancements |
China Unicom, ZTE Corporation, Samsung, Nokia, Lenovo |
| R3-250929 |
(BL CR to 38.423 for SON) Addition of SON enhancements |
ZTE Corporation, Samsung, Nokia, Lenovo, Jio |
| 10.2 |
MRO Enhancements |
|
| R3-250076 |
[TP for SON BL CR for TS 37.340] MRO Enhancements for optimisation of the S-CPAC selection |
Nokia |
| R3-250084 |
(TP for SON BL CR for TS 38.473, TP for SON BL CR for TS 37.340, TP for SON BL CR for TS 38.300) MRO Enhancements for LTM and CHO with Candidate SCG(s) |
Nokia |
| R3-250098 |
MRO enhancements for R18 mobility mechanisms |
Qualcomm Incorporated |
| R3-250167 |
(TP to BLCR of 38.473) Discussion on MRO for LTM |
NEC |
| R3-250239 |
(TP for SON BL CR for TS 38.473) Discussion on LTM MRO |
Google |
| R3-250246 |
(TP for BLCR for SON for 38.300, 38.401,38.473, 38.413, 37.340, 38.423) MRO enhancement for R18 mobility mechanisms |
Huawei |
| R3-250269 |
(TP for SON BLCR for 38.473) Discussion on MRO for LTM |
Lenovo |
| R3-250270 |
(TP for SON BLCR for 37.340) Discussion on MRO for subsequent CPAC and CHO with candidate SCG(s) |
Lenovo |
| R3-250325 |
(TP for 37.340, 38.473, 38.300 and 38.401) MRO for R18 mobility mechanisms |
CATT |
| R3-250407 |
(TP for BL CR to 38.473 for SON) MRO enhancements for LTM |
Ericsson |
| R3-250530 |
Discussion on Enhancements in SON/MDT Data Collection and Mobility Robustness Optimization (MRO) |
Jio Platforms (JPL) |
| R3-250606 |
(TP to BL CR TS38.401) MRO for LTM |
Samsung |
| R3-250610 |
(TP for SON BLCR TS38.300, TS37.340 and TS38.423) MRO for CHO with candidate SCGs and S-CPAC |
Samsung |
| R3-250611 |
Failure scenarios on MRO for CHO with candidate SCGs |
Samsung, Cybercore, Lenovo |
| R3-250724 |
(TP for 38.401 38.473 38.300)Discussion on MRO |
ZTE Corporation |
| R3-250734 |
Discussion on MRO Enhancements |
China Unicom |
| R3-250823 |
SoD of MRO for LTM |
Ericsson |
| R3-250824 |
SoD of MRO for others |
Samsung |
| R3-250853 |
(TP for SON BL CR for TS38.423) MRO for CHO with Candidate SCG(s) |
Samsung, Nokia, Ericsson, Lenovo, CATT, ZTE |
| R3-250854 |
(TP for SON BL CR for TS 37.340) MRO enhancement for CHO with Candidate SCG(s) |
Nokia, Samsung, CATT, ZTE |
| R3-250855 |
(TP for SON BL CR for TS38.300) MRO for CHO with Candidate SCG(s) |
ZTE Corporation, Samsung, Nokia, Lenovo |
| R3-250856 |
(TP for SON BL CR for TS38.300) MRO for S-CPAC |
Samsung |
| R3-250859 |
CB:#SONMDT1_LTM |
Ericsson |
| R3-250900 |
(TP for SON BLCR TS37.340) MRO for S-CPAC |
Samsung, Lenovo, CATT |
| 10.3.1 |
Intra-NTN Mobility |
|
| R3-250077 |
[TP to BL CR to 38.423, SON] Solution to avoid restarting MRO in NTN deployments |
Nokia |
| R3-250099 |
SON MDT for NTN |
Qualcomm Incorporated |
| R3-250180 |
Discussion on SON/MDT enhancements for NTN |
NEC |
| R3-250271 |
Discussion on MRO for intra-NTN mobility |
Lenovo |
| R3-250300 |
(TP for MDT BLCRs for TS38.413, TS38.423, TS37.320): SON for Intra-NTN mobility |
Huawei |
| R3-250326 |
(TP for 38.300 and 38.413) Intra-NTN mobility for SONMDT |
CATT |
| R3-250408 |
SON-MDT enhancements for NTN |
Ericsson |
| R3-250499 |
(TP to BL CR for 38.300) Further discussion on SONMDT enhancement for NTN |
ZTE Corporation |
| R3-250626 |
(TP for MDT BLCRs for TS38.413, TS38.423) SON enhancements for NTN |
Harman GmbH |
| R3-250666 |
Discussion on SONMDT enhancement for NTN |
CMCC, Huawei |
| R3-250735 |
Discussion on SONMDT enhancements for NTN mobility |
China Unicom |
| R3-250736 |
draft CR for TS 38.413 MDT enhancement for NTN |
China Unicom |
| R3-250738 |
(TP for MDT BLCRs for TS38.413, TS38.423) SON enhancements for NTN |
Samsung |
| R3-250825 |
SoD of SONMDT NTN related |
Huawei |
| 10.3.2 |
Network Slicing |
|
| R3-250078 |
[TP to BL CR to 38.300, MDT] MDT solution for slice support and slice-related mobility enhancements |
Nokia |
| R3-250100 |
SON MDT for network slicing |
Qualcomm Incorporated |
| R3-250247 |
SON and MDT for Network Slicing |
Huawei |
| R3-250327 |
Network slicing for SONMDT |
CATT |
| R3-250409 |
On MDT enhancements for Network Slicing |
Ericsson, Jio Platforms (JPL), Interdigital, FiberCop |
| R3-250410 |
(TP for BL CR to 38.413 for MDT) Addition of MDT enhancements [TP on deferred MDT] |
Ericsson, Jio Platforms (JPL), Interdigital, FiberCop |
| R3-250411 |
On SON enhancements for Network Slicing |
Ericsson |
| R3-250613 |
Discussion on MDT for Network Slicing |
Samsung, Lenovo, Cybercore |
| R3-250683 |
Discussion on SON/MDT for network slicing |
CMCC |
| R3-250725 |
Further consideration on SON/MDT for Slicing |
ZTE Corporation |
| R3-250737 |
Discussion on SONMDT enhancements for network slicing |
China Unicom |
| R3-250755 |
Reply LS on SON for Network Slicing and enhanced area scope |
SA5(Ericsson) |
| R3-250826 |
SoD of SONMDT slicing related |
ZTE |
| R3-250869 |
LS on SON for Network Slicing |
RAN3(ZTE) |
| R3-250914 |
LS on SON for Network Slicing |
RAN3(ZTE) |
| 10.4 |
R18 leftovers |
|
| R3-250248 |
(TP for BLCR for SON for 38.413, 36.423) Rel-18 SON and MDT leftovers |
Huawei |
| R3-250272 |
Discussion on MRO for R18 leftovers |
Lenovo |
| R3-250328 |
(TP for 37.340, 38.423, 36.423 and 38.413) SON enhancement for R18 leftover |
CATT |
| R3-250412 |
(TP for BL CR to 38.413 for SON) UHI for SCG activation and deactivation |
Ericsson |
| R3-250500 |
Further discussion on Rel-18 leftovers |
ZTE Corporation |
| R3-250612 |
(TP for SON BLCR for 38.423, 36.423 and TS37.340) Rel-18 SON and MDT leftovers |
Samsung |
| R3-250827 |
SoD of SONMDT leftovers |
CATT |
| R3-250850 |
(TP for SON BLCR for 38.423) MRO for MR-DC SCG failure |
Samsung |
| R3-250851 |
(TP for SON BLCR for 36.423) MRO for MR-DC SCG failure |
Samsung |
| 11.1 |
General |
|
| R3-250042 |
(BL CR to TS 38.423) Support of enhancements on AI/ML for NG-RAN |
ZTE Corporation, Qualcomm, China Unicom, Ericsson, Samsung, Nokia, Lenovo, CATT, Huawei, NEC, CMCC, China Telecom, Telecom Italia, Deutsche Telekom, Verizon Wireless, LGE, Jio, Rakuten |
| R3-250043 |
(BL CR to TS 38.473) Support of enhancements on AI/ML for NG-RAN |
Ericsson (Rapporteur), ZTE, NEC, Nokia |
| R3-250723 |
Work plan for Rel-19 Enhancements for AI/ML for NG-RAN |
ZTE Corporation, NEC |
| R3-250785 |
(BL CR to TS 38.473) Support of enhancements on AI/ML for NG-RAN |
Ericsson (Rapporteur), ZTE, NEC, Nokia |
| R3-250924 |
(BL CR to 38.423) Support of enhancements on AI/ML for NG-RAN |
ZTE Corporation, Qualcomm, China Unicom, Ericsson, Samsung, Nokia, Lenovo, CATT, Huawei, NEC, CMCC, China Telecom, Telecom Italia, Deutsche Telekom, Verizon Wireless, LGE, Jio, Rakuten |
| R3-250925 |
(BL CR to 38.473) Support of enhancements on AI/ML for NG-RAN |
Ericsson (Rapporteur), ZTE, NEC, Nokia, Huawei |
| 11.2 |
AI/ML enabled Slicing |
|
| R3-250088 |
AI/ML enabled slicing |
Ofinno, LLC |
| R3-250139 |
Discussion on AI/ML assisted Network Slicing |
ZTE Corporation |
| R3-250140 |
[TP to 38.423] AI/ML assisted Network Slicing |
ZTE Corporation, China Unicom, China Telecom |
| R3-250168 |
(TP for BLCR for TS38.300) Support of enhancements on AI/ML for NG-RAN |
NEC, ZTE, Qualcomm, Samsung, CMCC |
| R3-250169 |
UE performance feedback for AI/ML-based Slicing |
NEC |
| R3-250243 |
Discussion on remaining issues for NG-RAN AI/ML for Network Slicing |
Qualcomm Incorporated |
| R3-250258 |
Support for Slice level UE performance |
Tejas Network Limited, CEWiT |
| R3-250273 |
Way forward of per slice UE performance measurement |
Lenovo |
| R3-250372 |
(TP for AI/ML BLCR to TS 38.300, TP for AI/ML BLCR to TS 38.401, and TP for AI/ML BLCR to TS 37.340) Capturing agreements in Stage 2 RAN specifications |
Huawei |
| R3-250373 |
([Draft] LS to SA5 and TP for AI/ML BLCR to TS 38.423) Discussion on the AI/ML-based Network Slicing |
Huawei |
| R3-250461 |
Cell capacity class value for AI/ML enabled slicing |
Ericsson, Jio Platforms (JPL) |
| R3-250462 |
(TP to TS 38.423) Cell capacity class value for AI/ML enabled slicing |
Ericsson, Jio Platforms (JPL) |
| R3-250471 |
AI/ML enabled Network Slicing |
Ericsson |
| R3-250472 |
(TP for BL CR to TS 38.423) AI/ML enabled Network Slicing |
Ericsson |
| R3-250569 |
AI/ML Slicing Open Issues |
Nokia, Jio Platforms (JPL) |
| R3-250570 |
(TP to BLCR to TS 38.423) AI/ML Slicing |
Nokia, Jio Platforms (JPL) |
| R3-250592 |
(TP on 38.423)Support of AI/ML enabled Slicing |
CATT |
| R3-250594 |
Enhancement of UE performance metrics |
CATT, Jio, Qualcomm, CBN |
| R3-250616 |
Discussion on AI/ML enabled slicing |
Samsung |
| R3-250671 |
Discussion on AI-based network slice |
CMCC |
| R3-250672 |
(TP for 38.423) AIML based slice |
CMCC |
| R3-250718 |
Enhancement in Data Collection Request procedure for UE Performance Data |
Rakuten Mobile, Inc, CATT |
| R3-250720 |
UE Performance Granularity for AI/ML based Network Slicing |
Rakuten Mobile, Inc |
| R3-250721 |
[TP to BLCR 38.300] Support of AI/ML assisted Network Slicing |
ZTE Corporation, Lenovo, Samsung |
| R3-250786 |
CB:#AIRAN1_Slicing |
ZTE |
| R3-250874 |
[TP to 38.423] AI/ML assisted Network Slicing |
ZTE Corporation, China Unicom, China Telecom |
| R3-250889 |
[TP to BLCR 38.423] Support of AI/ML assisted Network Slicing |
ZTE Corporation, China Unicom, China Telecom, Ericsson, Nokia, Huawei, Ofinno, Samsung, Deutsche Telekom, CMCC, Lenovo, Qualcomm, NEC |
| 11.3 |
AI/ML enabled Coverage and Capacity Optimization |
|
| R3-250170 |
(TP to BLCR TS38.423 and TS38.473) Open issues for AI/ML-based CCO |
NEC |
| R3-250244 |
Discussion on remaining issues in AI/ML enabled CCO |
Qualcomm Incorporated |
| R3-250274 |
Discussion on AI/ML based CCO |
Lenovo |
| R3-250347 |
Discussion on AIML based Coverage and Capacity Optimization |
China Telecom |
| R3-250374 |
(TPs for AI/ML BLCR to TS 38.423 and AI/ML BLCR to TS 38.473) Discussion on the AI/ML-based Coverage and Capacity Optimization |
Huawei |
| R3-250380 |
Discussion on issues for AI/ML-based CCO |
LG Electronics Inc. |
| R3-250465 |
Further discussions on AI/ML enabled CCO |
Ericsson, Jio Platforms (JPL), InterDigital |
| R3-250466 |
(TP to 38.423) - AI/ML support for CCO |
Ericsson, Jio Platforms (JPL), InterDigital |
| R3-250467 |
(TP to 38.473) - AI/ML support for CCO |
Ericsson, Jio Platforms (JPL), InterDigital |
| R3-250468 |
AI/ML enabled CCO across multiple nodes |
Ericsson, Jio Platforms (JPL), InterDigital |
| R3-250532 |
(TP for BLCR to TS 38.473) Further discussion on energy efficient AI/ML-based CCO issue prediction in split architecture |
Nokia, FiberCop, Jio Platforms (JPL) |
| R3-250533 |
(TP for BLCR to TS 38.473) Further discussion on signalling for AI/ML-based CCO |
Nokia |
| R3-250581 |
Further Enhancements on AIML support for CCO |
Jio Platforms JPL |
| R3-250593 |
(TP on 38.423/38.473) Open issues on the CCO use case |
CATT |
| R3-250617 |
Discussion on AI/ML enabled CCO |
Samsung |
| R3-250673 |
Discussion on AI/ML-based CCO |
CMCC |
| R3-250700 |
[TP to 38.401] Support of AI/ML assisted CCO |
ZTE Corporation, Lenovo, China Unicom, China Telecom |
| R3-250701 |
[TP to 38.423 and 38.473] Support of AI/ML assisted Coverage and Capacity Optimization |
ZTE Corporation |
| R3-250702 |
Discussion on AI/ML assisted Coverage and Capacity Optimization |
ZTE Corporation |
| R3-250722 |
Conflict between legacy CCO and AI/ML-based CCO |
Rakuten Mobile, Inc |
| R3-250787 |
CB:#AIRAN2_CCO |
Huawei |
| R3-250804 |
(TPs for AI/ML BLCR to TS 38.473) Discussion on the AI/ML-based Coverage and Capacity Optimization |
Huawei |
| R3-250890 |
(TP for AI/ML BLCR to TS 38.473) Discussion on the AI/ML-based Coverage and Capacity Optimization |
Huawei, Lenovo, Qualcomm, ZTE, Samsung, FiberCop, Ericsson, LG Electronics, Deutsche Telekom, Nokia, NEC, CMCC |
| 11.4 |
R18 leftovers |
|
| R3-250089 |
Mobility Optimization for NR-DC |
Ofinno, LLC |
| R3-250141 |
(TP to 38.423) Addition of predicted PSCell ID within DC procedure |
ZTE Corporation, Samsung, Qualcomm, CATT, CMCC, China Unicom |
| R3-250142 |
(TP to 38.423) Discussion on Mobility Optimization for NR-DC |
ZTE Corporation |
| R3-250143 |
(TP to 38.473, 37.483) Discussion on split architecture |
ZTE Corporation |
| R3-250144 |
[Draft LS] Discussion on continuous MDT collection |
ZTE Corporation |
| R3-250171 |
Continuous MDT collection for AI/ML |
NEC |
| R3-250172 |
(TP to BLCR TS38.423) NR-DC mobility optimization |
NEC |
| R3-250173 |
(TP to BLCR TS38.473) Split architecture support |
NEC |
| R3-250245 |
Discussion on Continuous MDT |
Qualcomm Incorporated |
| R3-250275 |
Discussion on UE performance metric in AIML for NR-DC |
Lenovo |
| R3-250276 |
(TP to BLCR 38.473 and 37.483) Discussion on split architecture related issues for Rel18 use cases |
Lenovo |
| R3-250277 |
(TP to BLCR 37.340) AIML for NR-DC |
Lenovo, CATT, ZTE Corporation, Samsung |
| R3-250278 |
(TP to BLCR 38.401) AIML for RAN in split architecture |
Lenovo, CATT, ZTE Corporation |
| R3-250343 |
Discussion on AI/ML based Mobility Optimization for NR-DC |
China Telecom |
| R3-250344 |
(TP to TS38.423) Support of AIML based Mobility Optimization for NR-DC |
China Telecom |
| R3-250348 |
Discussion on Continuous MDT measurement |
China Telecom |
| R3-250375 |
(TP for AI/ML BLCR to TS 38.423) AI/ML-based Mobility Optimization in NR-DC |
Huawei |
| R3-250376 |
(TP for AI/ML BLCR to TS 38.473 and TP for AI/ML BLCR to TS 37.483) Split architecture support for Rel-18 “AI/ML for NG-RAN” use cases |
Huawei |
| R3-250377 |
([Draft LS to SA5]) On Continuous MDT for AI/ML |
Huawei, FiberCop |
| R3-250381 |
Discussion on open issue of mobility optimization for NR-DC |
LG Electronics Inc. |
| R3-250419 |
Down selection on the solution for continuous MDT |
CATT |
| R3-250455 |
Split architecture support for Release 18 use cases |
Ericsson, Nokia, Jio Platforms (JPL), Deutsche Telekom, FiberCop |
| R3-250456 |
(TP to 38.473) - Split architecture support for Release 18 use cases – addition of Data collection procedure |
Ericsson, Nokia, Jio Platforms (JPL), Deutsche Telekom, FiberCop |
| R3-250457 |
(TP to 38.473) - Split architecture support for Release 18 use cases – reuse of Resource Status Reporting |
Ericsson, Nokia, Jio Platforms (JPL), Deutsche Telekom, FiberCop |
| R3-250458 |
(TP to 37.483) - Split architecture support for Release 18 use cases |
Ericsson, Nokia, Jio Platforms (JPL), Deutsche Telekom, FiberCop |
| R3-250459 |
AI/ML support for NR-DC |
Ericsson, Jio Platforms (JPL), InterDigital, FiberCop |
| R3-250460 |
(TP to TS 38.423) AI/ML support for NR-DC |
Ericsson, Jio Platforms (JPL), InterDigital, FiberCop |
| R3-250463 |
Further discussions on Continuous MDT |
Ericsson, InterDigital, Deutsche Telekom, FiberCop |
| R3-250464 |
[Draft] LS on Continuous MDT |
Ericsson, InterDigital, Deutsche Telekom, FiberCop |
| R3-250538 |
Discussion on AIML energy saving for split architecture |
NTT DOCOMO INC.. |
| R3-250571 |
Energy Cost Measurement in Split Architecture |
Nokia, Deutsche Telekom, Jio Platforms (JPL), FiberCop |
| R3-250572 |
[Draft] LS on New Energy Consumption Measurement for gNB-DU |
Nokia, Deutsche Telekom, Jio Platforms (JPL), FiberCop |
| R3-250573 |
Procedures for AI/ML Mobility Optimization in NR-DC |
Nokia |
| R3-250574 |
(TP to TS 38.423) AI/ML Mobility for NR-DC |
Nokia |
| R3-250575 |
Discussion on Rel-18 UE Performance measurements |
Nokia |
| R3-250576 |
Continuous Management-based MDT Requirements |
Nokia, Deutsche Telekom, Jio Platforms (JPL) |
| R3-250577 |
[Draft] LS on Continuous MDT Requirements |
Nokia, Deutsche Telekom, Jio Platforms (JPL) |
| R3-250580 |
Discussions for AI/ML assisted NR-DC |
Jio Platforms JPL |
| R3-250595 |
AI/ML in DC scenario |
CATT |
| R3-250596 |
(TP for TS 38.423) Introducing essentially per-DRB UE performance result for DC |
CATT |
| R3-250597 |
(TP on 38.470/37.480) AI/ML in split gNBs |
CATT |
| R3-250618 |
Discussion on AI/ML for mobility in NR-DC |
Samsung |
| R3-250619 |
AI/ML for NG-RAN in split architecture |
Samsung |
| R3-250620 |
(CR to 37.483) AI/ML for NG-RAN on split architecture |
Samsung |
| R3-250621 |
Discussion on continuous MDT collection targeting the same UE across RRC states |
Samsung |
| R3-250664 |
Discussion on AIML based Mobility Optimization for NR-DC |
CMCC, CATT, ZTE Corporation, Lenovo |
| R3-250665 |
(TP to 38.423) AIML based Mobility Optimization for NR-DC |
CMCC |
| R3-250676 |
(TP to 38.473) Transfer Measured EC via F1 for split architecture |
CMCC, ZTE, CATT, Lenovo, Samsung |
| R3-250682 |
Discussion on UE performance metric for split architecture use cases |
CMCC |
| R3-250788 |
[Draft] LS on Continuous MDT |
RAN3(Ericsson) |
| R3-250789 |
CB:#AIRAN4_NRDC |
CMCC |
| R3-250790 |
CB:#AIRAN5_SplitArch |
Nokia |
| R3-250891 |
LS on Continuous MDT |
RAN3(Ericsson) |
| 12.1 |
General |
|
| R3-250044 |
(BL CR to 38.401 for WAB) Support for Wireless Access Backhaul |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung, Lenovo, Qualcomm |
| R3-250045 |
(BL CR to 38.300 for Femto) Introduction of NR Femto Architecture and Protocol Aspects |
Ericsson, Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells, ZTE, NEC |
| R3-250046 |
(BL CR to 38.410 for Femto) Introduction of NR Femto in NGAP list of functions |
ZTE Corporation, Nokia |
| R3-250047 |
(BL CR to TS 38.413) Support of NR Femto architecture with NR Femto Gateway |
Nokia, Huawei |
| R3-250943 |
(BL CR to 38.300 for Femto) Introduction of NR Femto Architecture and Protocol Aspects |
Ericsson, Nokia, TMO US, AT&T, Verizon Wireless, BT, Charter, Huawei, LG Electronics, Samsung, Lenovo, Baicells, ZTE, NEC |
| R3-250944 |
(BL CR to 38.305 for WAB) Support of Location Service Involving WAB-Nodes |
ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT, Samsung, Huawei, China Telecom |
| R3-250945 |
(BL CR to 38.401 for WAB) Support for Wireless Access Backhaul |
Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei, Samsung, Lenovo, Qualcomm, Jio Platforms |
| R3-250946 |
(BL CR to 38.413 for WAB) Additional ULI for UEs served by WAB-Nodes |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom, ZTE, Qualcomm, Samsung, CATT, Jio Platforms (JPL), Lenovo |
| R3-250947 |
(BL CR to 38.455 for WAB) Support of Location Service Involving WAB-Nodes |
Lenovo, ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, CATT, Samsung, Huawei, China Telecom, Jio Platforms (JPL) |
| 12.2 |
Wireless Access Backhaul (WAB) |
|
| R3-250016 |
LS on Location service of UEs served by MWAB |
SA2(Huawei) |
| R3-250062 |
(TP to 38.401) Discussion on multi hop prevention and additional ULI for WAB |
ZTE Corporation |
| R3-250063 |
(TP to 38.401 36.300) Discussion on supporting WAB |
ZTE Corporation |
| R3-250064 |
(TP to 38.305) Support of location service involving WAB-nodes |
ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT, Samsung |
| R3-250065 |
(TP to 38.455) Support of location service involving WAB-nodes |
ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT, Samsung |
| R3-250071 |
Reply LS on FS_VMR_Ph2 solution impacts to RAN (Access Control and Additional ULI) |
SA2(Ericsson) |
| R3-250073 |
Reply LS on FS_VMR_Ph2 solution impacts to RAN (MWAB mobility) |
SA2(Nokia) |
| R3-250102 |
(TP to BL CR 38.401 38.413) WAB architecture and mobility |
Qualcomm Inc. |
| R3-250103 |
BL draft CR to TS 38.300 on Support of WAB |
Qualcomm, Ericsson, CATT, ZTE, Nokia, Nokia Shanghai Bell |
| R3-250165 |
(TP to BL CR of 38.423 on WAB) Discussion on access and reliability for WAB |
NEC |
| R3-250211 |
Further consideration on support of WAB |
LG Electronics |
| R3-250212 |
(TP to TS 38.401, 38.413 and 38.423) TP for WAB support |
LG Electronics |
| R3-250219 |
(TP for TS 38.401) Discussion on NG management and Xn management for WAB |
Nokia, Nokia Shanghai Bell |
| R3-250220 |
(TP for TS 38.423 and TS 38.413) Discussion on WAB mobility |
Nokia, Nokia Shanghai Bell |
| R3-250232 |
(TPs for TS 38.413/38.423) Architecture, Access Control and Additional ULI for WAB |
Huawei |
| R3-250233 |
(TP for TS 38.401/38.455) Discussion on WAB related procedures |
Huawei |
| R3-250234 |
[draft] Reply LS on Location service of UEs served by MWAB |
Huawei |
| R3-250279 |
Architecture and configuration for WAB-node |
Lenovo |
| R3-250280 |
(TP to BL CR 38.401) Discussion on ULI and WAB node migration |
Lenovo |
| R3-250320 |
Discussion on enhancements for WAB |
CANON Research Centre France |
| R3-250356 |
(TP to BLCR for 38.401) On support of WAB |
CATT |
| R3-250357 |
(TP to BLCR for 38.423) Discussion on enhancements for WAB |
CATT |
| R3-250397 |
Discussion on RAN2 Impact of WAB |
China Telecom |
| R3-250398 |
Discussion on Multi-hop Prevention and Functionalities for WAB |
China Telecom |
| R3-250399 |
Discussion on Wireless Access Backhaul |
NTT DOCOMO INC. |
| R3-250511 |
Functional Aspects of WAB-Nodes |
Ericsson |
| R3-250512 |
(TP for WAB BL CR for TS 38.401): Functional Aspects of WAB-Nodes |
Ericsson |
| R3-250513 |
Discussion and [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (Access Control and Additional ULI) |
Ericsson |
| R3-250547 |
Discussion on WAB enhancements |
Jio Platforms (JPL) |
| R3-250627 |
(TP to BLCR for TS 38.410) Discussion on WAB mobility |
Samsung |
| R3-250628 |
Discussion on other aspects for the support of WAB |
Samsung |
| R3-250791 |
Summary of Offline Discussion on additional topological enhancement |
NTTDOCOMO, INC. |
| R3-250810 |
(CB: # WAB) LS to SA2 |
RAN3(ZTE) |
| R3-250813 |
(CB:#WAB) Summary of offline Discussion |
DoCoMo |
| R3-250828 |
(TP for WAB BL CR for TS 38.401) Functional Aspects of WAB-Nodes |
Ericsson |
| R3-250830 |
(TP for WAB BL CR for TS 38.401) WAB mobility |
CATT, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Samsung, Qualcomm, NTTDOCOMO |
| R3-250831 |
(TP for WAB BL CR to 38.305) Support of Location Service Involving WAB-Nodes |
ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT, Samsung, Huawei, China Telecom |
| R3-250832 |
(TP for WAB BL CR for TS 38.455) Support of Location Service Involving WAB-Nodes |
ZTE Corporation, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Lenovo, CATT, Samsung, Huawei, China Telecom |
| R3-250833 |
(TP for WAB BL CR for TS 38.413) Additional ULI for UEs served by WAB-Nodes |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom, ZTE, Qualcomm |
| R3-250834 |
LS on Additional ULI for UEs served by WAB-nodes |
RAN3(ZTE) |
| R3-250835 |
Reply LS on Support of Location Service Involving WAB-Nodes |
RAN3(Huawei) |
| R3-250897 |
(TP for WAB BL CR for TS 38.401): Functional Aspects of WAB-Nodes |
Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, Qualcomm, Lenovo, LG Electronics, NTTDOCOMO, ZTE |
| R3-250898 |
(TP for WAB BL CR for TS 38.401) WAB mobility |
CATT, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Samsung, Qualcomm, NTTDOCOMO, LGE, Jio |
| R3-250899 |
(TP for WAB BL CR for TS 38.413) Additional ULI for UEs served by WAB-Nodes |
Huawei, Ericsson, Nokia, Nokia Shanghai Bell, China Telecom, ZTE, Qualcomm, Samsung, CATT, Jio Platforms (JPL), Lenovo |
| R3-250901 |
Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) |
RAN3(ZTE) |
| R3-250902 |
Reply LS on Support of Location Service Involving WAB-Nodes |
RAN3(Huawei) |
| 12.3 |
5G Femto |
|
| R3-250020 |
Reply LS to request clarification on the potential baseline system architecture of 5G NR Femto |
SA2(LGE) |
| R3-250086 |
Discussion on Slice Feature and Access Control for NR Femto |
Baicells |
| R3-250087 |
TP to BL CR for TS 38.300 and TS 38.413 on NR Femto |
Baicells |
| R3-250174 |
Open issues for NR Femto |
NEC |
| R3-250209 |
Further discussion on access control in 5G Femto |
LG Electronics |
| R3-250210 |
(TP to TS 38.300 and 38.413) TP for access control in NR Femto |
LG Electronics |
| R3-250235 |
Discussion on functional split and remaining issues for NR Femto |
Huawei |
| R3-250236 |
(TP for BL CR for TS 38.300) Functional split for NR Femto |
Huawei |
| R3-250281 |
Discussion on remaining issues for NR Femto |
Lenovo |
| R3-250282 |
(TP to BL CR 38.300) Architecture and function split for NR Femto |
Lenovo |
| R3-250307 |
A Couple of Clarifications on NR Femto GW |
Ericsson |
| R3-250339 |
On Mobility for NR Femto |
China Telecom |
| R3-250358 |
Discussion on stage-2 NR Femto |
CATT |
| R3-250359 |
(TP to BLCR for 38.300) Introduction of Functional Split for NR Femto |
CATT |
| R3-250429 |
Discussion on functional split for NR Femto |
ZTE corporation |
| R3-250430 |
(TP for BLCR 38.300)NR Femto |
ZTE corporation |
| R3-250434 |
Completion of Functional Aspects of NR Femto |
Nokia |
| R3-250435 |
[TP for BL CR NR Femto 38.413] Completion of NR Femto Stage 3 |
Nokia, TMO US, AT&T, Docomo, BT |
| R3-250436 |
[TP for BL CR NR Femto 38.300] Functional aspects of NR Femto Gateway |
Nokia, TMO US, AT&T, Docomo, BT |
| R3-250437 |
[TP for BL CR NR Femto 38.300] Functional aspects of AMF |
Nokia, TMO US, AT&T, Docomo, BT |
| R3-250531 |
[TP to 38.300] Access Control for NR Femto |
Jio Platforms (JPL) |
| R3-250629 |
(TP to TS 38.300) Discussion on functional split for NR Femto |
Samsung |
| R3-250661 |
Discussion on 5G femto |
NTT DOCOMO INC. |
| R3-250759 |
[TP for BL CR NR Femto 38.300] Functional aspects of NR Femto Gateway |
Nokia, TMO US, AT&T, Docomo, BT |
| R3-250760 |
[TP for BL CR NR Femto 38.300] Functional aspects of AMF |
Nokia, TMO US, AT&T, Docomo, BT |
| R3-250792 |
LS on security verification related to NR Femtos |
RAN3(ZTE) |
| R3-250797 |
(TP for BL CR for TS 38.300) Functional of AMF for NR Femto |
Huawei |
| R3-250802 |
[TP for BL CR NR Femto 38.300] Functional aspects of NR Femto Gateway |
Nokia, TMO US, AT&T, Docomo, BT |
| R3-250817 |
(TP for BL CR NR Femto TS 38.300) Functional Aspects of NR Femto Gateway |
Nokia, TMO US, AT&T, BT, Docomo, Verizon Wireless, Ericsson, Huawei, ZTE |
| R3-250821 |
(TP for BL CR for TS 38.300) Functional of AMF for NR Femto |
Huawei, Lenovo, Nokia, Samsung, ZTE, China Telecom |
| R3-250822 |
LS on security verification related to NR Femtos |
RAN3(ZTE) |
| 13.1 |
General |
|
| R3-250008 |
RAN2 agreements on Inter-CU LTM and Conditional LTM |
RAN2(Lenovo) |
| R3-250048 |
(BL CR to 37.483) Introducing Rel-19 Mobility enhancement |
LG Electronics Inc., Nokia, China Telecom, Google, Ericsson, CATT, Qualcomm, Samsung, CMCC, ZTE, Huawei, NTT Docomo, Lenovo, NEC |
| R3-250049 |
(BL CR to 38.420) Support for Inter-CU LTM |
ZTE Corporation, China Telecom, Samsung, Nokia, CATT, NEC, LG Electronics, Ericsson, Huawei, Lenovo |
| R3-250050 |
(BL CR to 38.300) Support for Inter-CU LTM |
Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung |
| R3-250051 |
(BL CR to 38.423) Xn support for inter-CU LTM |
Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics |
| R3-250931 |
(BL CR to 37.340) stage 2 for inter-CU LTM in NR-DC |
CATT, China Telecom, Huawei, Nokia, LG Electronics, Google, Samsung, Ofinno, Ericsson, Lenovo, NEC, ZTE |
| R3-250932 |
(BL CR to 37.483) Introducing Rel-19 Mobility enhancement |
LG Electronics Inc., Nokia, China Telecom, Google, Ericsson, CATT, Qualcomm, Samsung, CMCC, ZTE, Huawei, NTT Docomo, Lenovo, NEC, Ofinno, Jio Platforms (JPL) |
| R3-250933 |
(BL CR to 38.300) Support for Inter-CU LTM |
Nokia, Huawei, Google, China Telecom, NEC, Ericsson, LGE, ZTE, CATT, Samsung, Offino |
| R3-250934 |
(BL CR to 38.401) on conditional intra-CU LTM |
China Telecom, ZTE Corporation, NEC, Samsung, Nokia, Google, Huawei, Ericsson, LG Electronics |
| R3-250935 |
(BL CR to 38.423) Xn support for inter-CU LTM |
Ericsson, Samsung, Nokia, China Telecom, CATT, Huawei, Google, Lenovo, NEC, ZTE, LG Electronics, Ofinno |
| R3-250936 |
(BL CR to 38.473) Inter-CU LTM |
Huawei, Nokia, Samsung, Google, NEC, China Telecom, Ericsson, LG Electronics, CATT, Ofinno, ZTE, Lenovo |
| 13.2 |
Support for inter-CU LTM |
|
| R3-250058 |
Discussion on Inter-gNB-CU LTM Procedure |
Nokia |
| R3-250059 |
Discussion on Inter-gNB-CU LTM Dual Connectivity |
Nokia |
| R3-250090 |
Issues on Data Forwarding for Inter-CU LTM |
Ofinno, LLC |
| R3-250116 |
(TP to TS38.423) inter-CU LTM |
ZTE Corporation |
| R3-250117 |
(TP to TS37.340 and TS38.423) SN initiated inter-CU SCG LTM |
ZTE Corporation |
| R3-250160 |
(TP to BL CR for TS 38.423 on Inter-CU LTM) Rel-19 inter-CU LTM issues |
NEC |
| R3-250161 |
discussion Rel-19 inter-CU LTM in DC scenario |
NEC |
| R3-250192 |
Signalling enhancements for inter-CU LTM HO |
Qualcomm Incorporated |
| R3-250227 |
Initial considerations on Inter-CU LTM |
Rakuten Mobile, Inc |
| R3-250238 |
(TP to BL CR to 38.300 and 38.423) Support for reference configurations for inter-CU LTM |
Google |
| R3-250259 |
gNB-DU initiated LTM candidate cell reconfiguration |
Rakuten Mobile, Inc |
| R3-250263 |
gNB-DU initiated LTM candidate cell reconfiguration |
Rakuten Inc, Qualcomm Inc |
| R3-250283 |
[TP to BLCR for TS 38.423] Inter-CU LTM |
Lenovo |
| R3-250284 |
General aspects of inter-CU SCG LTM |
Lenovo |
| R3-250297 |
(TP for LTM BLCR for TS38.473): Further discussion on inter-CU LTM procedure |
Huawei |
| R3-250298 |
(TP for LTM BLCR for TS38.300): Update on inter-CU LTM basic procedure |
Huawei |
| R3-250340 |
Discussion on signaling enhancement for inter-CU LTM |
China Telecom |
| R3-250341 |
Discussion on support of inter-CU LTM in NR-DC scenario |
China Telecom |
| R3-250365 |
Further discussion on inter-CU LTM |
Ericsson |
| R3-250366 |
(TP for TS 38.300, TS 38.423, TS 37.340) – Support for inter-CU LTM |
Ericsson |
| R3-250415 |
Discussion for Inter-CU LTM |
CATT |
| R3-250416 |
(TP to 37.340) Discussion for Inter-CU LTM in DC |
CATT |
| R3-250529 |
Discussion on Inter-CU LTM Dual Connectivity |
Jio Platforms (JPL) |
| R3-250539 |
Discussion on inter-CU LTM non-DC case |
NTT DOCOMO INC.. |
| R3-250540 |
Discussion on inter-CU LTM DC case |
NTT DOCOMO INC.. |
| R3-250640 |
Discussion on Inter-gNB-CU LTM |
Samsung |
| R3-250641 |
(TP to BLCR for TS 38.423) Xn impact for Inter-gNB-CU LTM |
Samsung |
| R3-250647 |
Keep continuing discussions on Inter-CU LTM signaling design |
LG Electronics Inc. |
| R3-250689 |
Discussion on inter-CU LTM |
CMCC |
| R3-250807 |
CB:#MobilityEnh_LTM |
China Telecom |
| R3-250884 |
(TP for LTM BLCR for TS38.473):Inter-CU LTM |
Huawei, Nokia, Samsung, Google, NEC, China Telecom, Ericsson,
LG Electronics, CATT, Ofinno, ZTE, Lenovo |
| R3-250885 |
(TP to BL CR for TS 38.300) Inter-CU LTM Procedure |
Nokia, Samsung, Huawei, Ericsson, LG Electronics, CATT, Ofinno, ZTE, NEC |
| R3-250892 |
(TP for LTM BL CR for TS 38.423) – Support for inter-CU LTM |
Ericsson, Ofinno, LG Electronics, Google, NEC, Huawei, Nokia, CATT, ZTE |
| R3-250894 |
(TP for BL CR for TS 37.483) Inter-CU LTM |
LG Electronics, Nokia, China Telecom, Google, Ericsson, CATT, Qualcomm, Samsung, CMCC, ZTE, Huawei, NTT Docomo, Lenovo, NEC |
| R3-250896 |
(TP to 37.340) stage 2 for inter-CU LTM in NR-DC |
CATT, China Telecom, Huawei, Nokia, LG Electronics, Google, Samsung, Ofinno, Ericsson, Lenovo, NEC, ZTE |
| R3-250904 |
(TP for NR_Mob_Ph4 TS 37.483) Inter-CU LTM |
LG Electronics, Nokia, China Telecom, Google, Ericsson, CATT, Qualcomm, Samsung, CMCC, ZTE, Huawei, NTT Docomo, Lenovo, NEC, Ofinno |
| 13.3 |
Support for Conditional LTM |
|
| R3-250060 |
Discussion on Conditional LTM in disaggregated gNB architecture |
Nokia |
| R3-250162 |
Discussion of Rel-19 intra-CU Conditional LTM |
NEC |
| R3-250191 |
signaling enhancements for Conditional Intra-gNB/Intra-CU LTM |
Qualcomm Incorporated |
| R3-250285 |
[TP to BL CR for TS 38.401] Support for conditional intra-CU LTM |
Lenovo |
| R3-250299 |
(TP for LTM BLCR for TS38.473): Comprehensive analysis of intra-CU conditional LTM |
Huawei |
| R3-250342 |
(TP for TS38.401) On support of intra-CU Conditional LTM |
China Telecom |
| R3-250367 |
Intra-CU Conditional LTM |
Ericsson |
| R3-250417 |
(TP to 38.473,38.401)Discussion for C-LTM |
CATT |
| R3-250585 |
Discussion on Conditional LTM |
Samsung |
| R3-250642 |
Discussion on Conditional LTM |
Samsung |
| R3-250645 |
Discussions on RAN3 impacts from Conditional Intra-CU LTM |
LG Electronics Inc. |
| R3-250646 |
(TP for NR_Mob_Ph4 TS 38.401 and TS 38.473) Conditional LTM |
LG Electronics Inc. |
| R3-250703 |
TP to TS 38.401 on conditional intra-CU LTM |
ZTE Corporation |
| R3-250808 |
CB:#MobilityEn_ConditionalLTM |
ZTE |
| R3-250875 |
TP to TS 38.401 on conditional intra-CU LTM |
ZTE Corporation |
| R3-250911 |
(TP to TS 38.401) on conditional intra-CU LTM |
ZTE Corporation, NEC, China Telecom, Samsung, Nokia, Google, Huawei, Ericsson |
| R3-250915 |
(TP to TS 38.401) on conditional intra-CU LTM |
ZTE Corporation, NEC, China Telecom, Samsung, Nokia, Google, Huawei, Ericsson, LGE |
| 14.1 |
General |
|
| R3-250052 |
(BL CR to 38.410) Introduce NG Removal procedure |
CMCC, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Qualcomm, Xiaomi, LG Electronics, China Telecom, Samsung, ZTE, NEC, ETRI |
| R3-250053 |
(BL CR to 38.300) Support for Regenerative Payload and MBS broadcast in NR NTN |
Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics, NEC, Lenovo, ETRI |
| R3-250054 |
Support for Regenerative Payload and MBS broadcast in NR NTN |
CATT, Thales, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Qualcomm, Samsung, Xiaomi, CMCC, China Telecom, Jio, LG Electronics, NEC, ETRI, SES, ESA |
| R3-250937 |
(BL CR to 38.300) Support for Regenerative Payload and MBS broadcast in NR NTN |
Ericsson, Thales, Deutsche Telekom, Nokia, ESA, CATT, ZTE, Sateliot, Huawei, Dish Networks, Echostar, Eutelsat Group, Xiaomi, Samsung, CMCC, LG Electronics, NEC, Lenovo, ETRI |
| R3-250938 |
(BL CR to 38.413) Support for Regenerative Payload and MBS broadcast in NR NTN |
CATT, Thales, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Qualcomm, Samsung, Xiaomi, CMCC, China Telecom, Jio, LG Electronics, NEC, ETRI, SES, ESA |
| 14.2 |
Support MBS broadcast service |
|
| R3-250011 |
Reply LS on supporting MBS broadcast service for NR NTN |
RAN2(Xiaomi) |
| R3-250072 |
Reply LS on Supporting MBS broadcast service for NR NTN |
SA2(Xiaomi) |
| R3-250106 |
(TP to BL CR for TS38.413) Support of MBS broadcast service for NR NTN |
CATT |
| R3-250134 |
Discussion on Support of MBS Broadcast Service |
TCL |
| R3-250151 |
(TP for TS 38.413) Support of broadcast service |
Xiaomi |
| R3-250181 |
(TP for TS 38.300 and TS 38.413) Discussion on NR NTN supporting MBS broadcast service |
NEC |
| R3-250221 |
(TP to BL CR for TS 38.300 and TS 38.413) Update on the support of MBS Broadcast Service |
Nokia, Nokia Shanghai Bell |
| R3-250309 |
Intended Service Area for MBS Broadcast |
Ericsson, Thales, Jio Platforms Limited, Intelsat |
| R3-250334 |
Support of MBS broadcast service for NTN |
China Telecom |
| R3-250400 |
(TP for TS 38.300 and TS 38.413) Support MBS broadcast service |
Huawei, Qualcomm Incorporated |
| R3-250501 |
(TPs to BL CR 38.300 and 38.413) Discussion on NTN broadcast service supporting |
ZTE Corporation |
| R3-250633 |
Further discussion on support broadcast service for NR NTN |
Samsung |
| R3-250675 |
(TP to 38.300) Discussion on Supporting MBS broadcast service for NR NTN |
CMCC |
| R3-250864 |
Summary of Offline Discussion on MBS for NTN |
Ericsson |
| R3-250870 |
(TP to BL CR 38.300) NTN broadcast service supporting |
ZTE Corporation, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm, CATT |
| R3-250871 |
(TP for BL CR TS 38.413) Support MBS broadcast service |
Huawei, Qualcomm, Nokia, Nokia Shanghai Bell |
| R3-250893 |
(TP for BL CR TS 38.413) Support MBS broadcast service |
Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Ericsson, Xiaomi, ZTE, CATT |
| 14.3 |
Support of Regenerative payload |
|
| R3-250023 |
LS on reply to LS on OAM requirements to support regenerative payload |
SA2(Huawei) |
| R3-250030 |
LS reply on OAM requirements to support regenerative payload |
SA5(CATT) |
| R3-250107 |
(TP to NTN BL CRs) Support of regenerative payload |
CATT |
| R3-250133 |
Discussion on Support of NTN Regenerative Architecture |
TCL |
| R3-250152 |
Support of Inactive UE mobility in NTN |
Xiaomi, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-250153 |
(TP for TS 38.300) Support of regenerative payload |
Xiaomi |
| R3-250182 |
(TP for TS 38.300) Discussion on regenerative payload enhancement for NR NTN |
NEC |
| R3-250222 |
(TP to BL CR for TS 38.300) Discussion on the support of Regenerative payload |
Nokia, Nokia Shanghai Bell |
| R3-250240 |
Discussion on Reply LS on OAM requirements to support Regenerative payload |
Qualcomm Incorporated, Vodafone Group Plc, Vodafone Telekomünikasyon A.S. |
| R3-250241 |
(TP for TS 38.300) Discussion on NR NTN Regenerative Payload |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Xiaomi |
| R3-250308 |
(TP for BL CR for TS 38.300) Stage 2 Corrections |
Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Thales, CATT, Qualcomm Incorporated, LG Electronics |
| R3-250310 |
Considerations on NG Interface Management over the Feeder Link |
Ericsson, Thales, Huawei, Jio Platforms Limited, Intelsat, ESA |
| R3-250311 |
Making the Case for Location-Based CHO in Rel-19 |
Ericsson, Thales, ESA, Inmarsat, Viasat, Jio Platforms Limited, Intelsat |
| R3-250312 |
Location-Based CHO in Rel-19 - XnAP Impacts |
Ericsson, Thales, ESA, Inmarsat, Viasat, Jio Platforms Limited, Intelsat |
| R3-250313 |
Additional Background on OAM Requirements and Regenerative Payload |
Ericsson |
| R3-250314 |
Inactive UEs and NR NTN |
Ericsson |
| R3-250335 |
Discussion on regenerative payload enhancement |
China Telecom |
| R3-250350 |
Discussion on regenerative NTN payload enhancement |
China Telecom |
| R3-250351 |
(TP for TS 38.300) Support of regenerative payload |
China Telecom |
| R3-250401 |
(TP for TS 38.300) Support of regenerative payload |
Huawei, Ericsson |
| R3-250402 |
[draft] Reply LS on OAM requirements to support regenerative payload |
Huawei |
| R3-250502 |
(TPs to BL CR 38.410 and 38.413) Discussion on support of regenerative payload |
ZTE Corporation |
| R3-250582 |
NG Interface Management with NGAP Removal |
Jio Platforms JPL |
| R3-250583 |
Discussion on Support of Inactive UE in NTN |
ETRI, Ajou University |
| R3-250634 |
Further discussion on support of regenerative payload for NR NTN |
Samsung |
| R3-250648 |
Discussions on INACTIVE support from moving satellite gNBs |
LG Electronics Inc. |
| R3-250649 |
(TP for NR_NTN_Ph3 TS 38.300 BL CR) OAM for NG management |
LG Electronics Inc. |
| R3-250650 |
Discussion on support of regenerative payload for NR NTN |
CSCN |
| R3-250681 |
Discussion on Support of regenerative payload for NR NTN |
CMCC |
| R3-250844 |
CB:#NRNTN2_regenerative |
CATT |
| R3-250877 |
Reply LS on OAM requirements to support regenerative payload transport links |
RAN3(CATT) |
| R3-250895 |
Reply LS on OAM requirements to support regenerative payload transport links |
RAN3(CATT) |
| 15.1 |
General |
|
| R3-250503 |
Updated Work Plan for IoT NTN |
ZTE Corporation, CATT, MediaTek.Inc |
| R3-250922 |
(BL CR to 36.410) Support of Full eNB as Regenerative payload |
Samsung, Ericsson, Sateliot, Thales, ESA, Deutsche Telekom, Jio Platforms Limited, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| 15.2 |
Support Full eNB as Regenerative Payload |
|
| R3-250014 |
Reply LS on PWS support for NB-IoT NTN |
SA1(Novamint) |
| R3-250154 |
Support of full eNB as regenerative payload |
Xiaomi |
| R3-250223 |
Discussion on the support of S&F in IoT NTN |
Nokia, Nokia Shanghai Bell |
| R3-250224 |
(TP for TS 36.412 and TS 36.413) Discussion on the support of regenerative architecture |
Nokia, Nokia Shanghai Bell |
| R3-250242 |
Discussion on Support for IoT NTN for Regenerative Payload |
Qualcomm Incorporated |
| R3-250315 |
How to Specify Store & Forward (S&F) Architecture in RAN3 |
Ericsson, Sateliot, Thales, ESA, Deutsche Telekom, Jio Platforms Limited, Qualcomm Incorporated |
| R3-250316 |
Store & Forward (S&F) Architecture - Stage 2 Impacts |
Ericsson, Sateliot, Thales, ESA, Deutsche Telekom, Jio Platforms Limited, Qualcomm Incorporated |
| R3-250317 |
Store & Forward (S&F) Architecture - S1 Removal |
Ericsson, Sateliot, Thales, ESA, Deutsche Telekom, Jio Platforms Limited, Qualcomm Incorporated |
| R3-250318 |
Store & Forward (S&F) Architecture - S1AP Impacts |
Ericsson, Sateliot, Thales, ESA, Deutsche Telekom, Jio Platforms Limited, Qualcomm Incorporated |
| R3-250319 |
PWS Support for NB-IoT NTN |
Ericsson |
| R3-250333 |
Support for IoT NTN with regenerative payload |
China Telecom |
| R3-250349 |
Support for IoT NTN with regenerative payload |
China Telecom |
| R3-250403 |
(TP for TS 36.300 and LS to SA2) Support of Full eNB as Regenerative Payload |
Huawei |
| R3-250404 |
[DRAFT] Reply LS on Support of Regenerative-based Satellite Access |
Huawei |
| R3-250405 |
Support of Full eNB as Regenerative Payload |
Huawei, Ericsson, Thales, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-250421 |
Discussion about IoT NTN for regeneration payload |
CATT |
| R3-250422 |
(Draft LS) Discussion about IoT NTN for S&F |
CATT |
| R3-250423 |
(TP to TS36.413) Introduce S1 Removal for IoT NTN |
CATT,ZTE,CMCC, SAMSUNG |
| R3-250504 |
Further discussion on support of store and forward satellite operation for IoT NTN |
ZTE Corporation |
| R3-250505 |
Support of full eNB as regenerative payload and Store&Forward mechanism for IoT NTN |
ZTE Corporation, Samsung, CMCC, CATT |
| R3-250635 |
Further discussion on support of regenerative payload for IoT NTN |
Samsung |
| R3-250674 |
(TP to 36.410) Introduce S1 Removal to support Regenerative Payload in IoT NTN |
CMCC, ZTE, Samsung, CATT |
| R3-250680 |
Discussion on Support of IoT NTN |
CMCC |
| R3-250846 |
CB:#IoTNTN |
ZTE Corporation |
| R3-250861 |
Support of full eNB as regenerative payload and Store&Forward mechanism for IoT NTN |
ZTE Corporation, Samsung, CMCC, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Xiaomi, Qualcomm |
| R3-250862 |
Support of Full eNB as Regenerative Payload |
Huawei, Ericsson, Thales, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-250863 |
(TP for TS 36.410) Add S1 Removal |
Ericsson, Sateliot, Thales, ESA, Deutsche Telekom, Jio Platforms Limited, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-250903 |
Support of Full eNB as Regenerative Payload |
Huawei, Ericsson, Thales, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Jio |
| 16.1 |
General |
|
| R3-250684 |
Work Plan for Ambient IoT Work Item |
CMCC, Huawei, T-Mobile USA |
| R3-250919 |
(BL CR to 38.300) Introduction of Ambient IoT |
CMCC, Huawei |
| R3-250920 |
(BL CR to 38.410) Introduction of Ambient IoT |
ZTE Corporation, China Telecom, Huawei, Samsung, CMCC, Nokia, Xiaomi |
| R3-250921 |
(BL CR to 38.413) Introduction of Ambient IoT |
Huawei |
| 16.2 |
RAN Architecture and Procedures |
|
| R3-250095 |
Architecture, Protocols and Signaling to support Topology 1 of A-IoT |
Qualcomm Incorporated |
| R3-250096 |
Inventory and Command procedures for Topology 1 of A-IoT |
Qualcomm Incorporated |
| R3-250108 |
(TP to BL CR for TS 38.300) A-IoT protocol stack |
CATT |
| R3-250109 |
(TP to BL CR for XXAP) A-IoT Information exchange between A-IoT CN and A-IoT RAN |
CATT |
| R3-250110 |
Discussion on A-IoT reader selection |
CATT |
| R3-250118 |
Discussion on RAN Architecture |
ZTE Corporation |
| R3-250119 |
Discussion on A-IoT procedures and content |
ZTE Corporation |
| R3-250120 |
Discussion on reader selection |
ZTE Corporation |
| R3-250147 |
Discussion on support of AIoT |
Xiaomi |
| R3-250148 |
(TP for TS 38.413) Support of AIoT |
Xiaomi |
| R3-250149 |
(TPs for TS 38.410 and TS 38.412) Support of AIoT |
Xiaomi |
| R3-250183 |
Discussion on AIoT architecture aspects |
NEC |
| R3-250184 |
Discussion on AIoT procedures aspects |
NEC |
| R3-250197 |
(TPs for TS 38.300, TS 38.410 BL CRs) Ambient IoT RAN Architecture |
Huawei, China Telecom, Lenovo, China Unicom |
| R3-250198 |
(TP for TS 38.413 BL CR) NG Interface Management for Ambient IoT |
Huawei, China Telecom, China Unicom |
| R3-250199 |
(TPs to TS 38.413 TS 38.410 BL CRs) A-IoT Inventory procedures |
Huawei, China Telecom, China Unicom |
| R3-250200 |
(TPs to TS 38.410 TS 38.413 BL CRs) A-IoT Command procedures |
Huawei, China Telecom, China Unicom |
| R3-250286 |
On A-IOT Architecture and Interface |
Lenovo |
| R3-250287 |
On A-IOT Inventory Procedure |
Lenovo |
| R3-250288 |
On A-IOT Command Procedure |
Lenovo |
| R3-250336 |
A-IoT architecture aspects |
China Telecom |
| R3-250352 |
A-IoT architecture aspects |
China Telecom |
| R3-250438 |
Ambient IoT Architecture |
Nokia |
| R3-250439 |
Signalling Information Elements for Inventory |
Nokia |
| R3-250440 |
Signalling Information Elements for Command |
Nokia |
| R3-250441 |
[TP for BL CR 38.410] AIoT procedures |
Nokia |
| R3-250444 |
[TP for BL CR 38.300 and 38.401] Architecture for A-IoT RAN |
Ericsson |
| R3-250445 |
[TP for BL CR 38.413] NGAP protocol elemets for A-IoT |
Ericsson |
| R3-250446 |
[DRAFT] Reply LS on A-IoT Conclusions in SA WG2 |
Ericsson |
| R3-250636 |
Discussion on RAN architecture and procedures for AIoT |
Samsung |
| R3-250643 |
Discussion on Signalling Procedure for Inventory and Command |
China Telecom |
| R3-250685 |
(TP to TS 38.300) Discussion on RAN Architecture for Ambient IoT |
CMCC |
| R3-250686 |
Discussion on Inventory Procedure and Signaling |
CMCC |
| R3-250687 |
Discussion on Command Procedure and Signalling |
CMCC |
| R3-250745 |
Discussion on Ambient IoT RAN Architecture |
China Unicom |
| R3-250794 |
CB:#AIoT1_General |
Huawei |
| R3-250814 |
[Draft] LS on Ambient IoT progress of RAN3 |
RAN3(Huawei) |
| R3-250815 |
(TP to TS 38.300 BL CR) A-IoT Architecture aspects |
CMCCCMCC, Huawei, ZTE |
| R3-250816 |
(TP for TS 38.410 BL CR) AIoT Architecture Aspects |
Nokia, Huawei, China Telecom, Xiaomi, ZTE |
| R3-250818 |
(TP to TS 38.300 BL CR) Support of Inventory and command |
Ericsson, Huawei, Nokia, ZTE, CMCC, Xiaomi |
| R3-250819 |
(TP to TS 38.410 BL CR) Support of Inventory and command |
ZTE |
| R3-250820 |
(TP to TS 38.413 BL CR) Support of Inventory and command |
Huawei, China Telecom, China Unicom, Nokia, CATT, ZTE, Xiaomi |
| R3-250905 |
LS on Ambient IoT progress of RAN3 |
RAN3(Huawei) |
| R3-250906 |
(TP to TS 38.300 BL CR) A-IoT Architecture aspects |
CMCC, Huawei, ZTE |
| R3-250907 |
(TP for TS 38.410 BL CR) AIoT Architecture Aspects |
Nokia, Huawei, China Telecom, Xiaomi, ZTE |
| R3-250908 |
(TP to TS 38.300 BL CR) Support of Inventory and command |
Ericsson, Huawei, Nokia, ZTE, CMCC, Xiaomi, Jio Platforms, NEC |
| R3-250909 |
(TP to TS 38.410 BL CR) Support of Inventory and command |
ZTE Corporation, China Telecom, Huawei, Samsugn, CMCC |
| R3-250910 |
(TP to TS 38.413 BL CR) Support of Inventory and command |
Huawei, China Telecom, China Unicom, Nokia, CATT, ZTE, Xiaomi |
| 16.3 |
Location Report |
|
| R3-250097 |
Locating Ambient IoT devices |
Qualcomm Incorporated |
| R3-250111 |
Discussion on locating of A-IoT device |
CATT |
| R3-250121 |
Discussion on Location Report |
ZTE Corporation |
| R3-250150 |
Discussion on location of the device |
Xiaomi |
| R3-250185 |
Discussion on AIoT location reporting aspects |
NEC |
| R3-250201 |
(TP for TS 38.413) A-IoT Device Locating |
Huawei, China Telecom, Lenovo, China Unicom |
| R3-250447 |
[TP for BL CR 38.413] On Location Reporting at reader ID granularity |
Ericsson |
| R3-250637 |
Discussion on Location report for AIoT |
Samsung |
| R3-250688 |
Discussion on A-IoT device location reporting |
CMCC |
| R3-250719 |
Discussion on support of location report |
LG Electronics |
| R3-250795 |
CB:#AIoT2_LocationReport |
Qualcomm |
| 17.1 |
General |
|
| R3-250055 |
(BL CR to 38.423) Introduction of Network Energy Saving Enhancement |
Ericsson, Huawei, CMCC, Samsung, Qualcomm, Nokia, ZTE, Lenovo, Deutsche Telekom, NEC |
| R3-250056 |
(BL CR to 38.473) Introduction of Network Energy Saving Enhancement |
Huawei, Ericsson, CMCC, Samsung, ZTE, Nokia, Deutsche Telekom, Lenovo, NEC, Jio |
| R3-250548 |
WI Work plan for R19 Network Energy Savings |
Ericsson |
| R3-250923 |
(BL CR to 38.423) Introduction of Network Energy Saving Enhancement |
Ericsson, Huawei, CMCC, Samsung, Qualcomm, Nokia, ZTE, Lenovo, Deutsche Telekom, NEC |
| 17.2 |
Support on-demand SSB SCell operation |
|
| R3-250129 |
(TP to BLCR for TS 38.473) Discussion on on-demand SSB SCell operation |
Huawei |
| R3-250175 |
Support on-demand SSB operation |
NEC |
| R3-250289 |
Discussion on On-demand SSB for SCell |
Lenovo |
| R3-250337 |
(TP to 38.473) On support on-demand SSB SCell operation |
China Telecom |
| R3-250360 |
(TP to BLCR for 38.300) Introduction of On-demand SIB1 |
CATT, Ericsson, Huawei, Samsung, China Telecomm, Rakuten |
| R3-250361 |
(TP to BLCR for 38.473) On support on-demand SSB SCell operation |
CATT |
| R3-250506 |
Further discussion on on-demand SSB Scell operation |
ZTE Corporation |
| R3-250522 |
TP to BL CR for TS 38.473) Discussion on On-Demand SSB SCell Operation |
CMCC |
| R3-250551 |
On-demand SSB SCell operation and other Energy Saving topics |
Ericsson |
| R3-250607 |
Discussion on on-demand SSB SCell operation in low-carbon green network |
Samsung |
| R3-250697 |
Discussion on OD-SSB based NES from neighbour gNB’s perspective |
Rakuten Mobile, Inc |
| R3-250800 |
CB:#ES1 |
Huawei |
| 17.3 |
Support on-demand SIB1 for UEs |
|
| R3-250104 |
Aspects of on-demand SIB1 for NES enhancements |
Qualcomm Inc. |
| R3-250130 |
(TP to BLCR for TS 38.473 and TS 38.423) Discussion on on-demand SIB1 for UEs in idle or inactive mode |
Huawei |
| R3-250176 |
Support on-demand SIB1 |
NEC |
| R3-250202 |
On-demand SIB1 for UEs in idle/inactive mode |
Fujitsu |
| R3-250290 |
Discussion on On-demand SIB1 for Idle/Inactive UE |
Lenovo |
| R3-250338 |
On support on-demand SIB1 |
China Telecom |
| R3-250362 |
(TP to BLCR for XnAP/F1AP) On support on-demand SIB1 for idle UE |
CATT, Fujitsu |
| R3-250507 |
Further discussion on on-demand SIB1 |
ZTE Corporation |
| R3-250523 |
Support On-Demand SIB1 for UEs |
CMCC |
| R3-250534 |
Xn and F1 signalling for On-Demand SIB1 |
Nokia |
| R3-250549 |
Xn impact of On-demand SIB1 for UEs in idle/inactive mode |
Ericsson, Deutsche Telekom, China Unicom |
| R3-250550 |
F1 impact of On-demand SIB1 for UEs in idle/inactive mode |
Ericsson, Deutsche Telekom, China Unicom, Rakuten |
| R3-250608 |
Discussion on on-demand SIB1 in low-carbon green network |
Samsung |
| R3-250609 |
Introduction of Network Energy Saving Enhancement |
Samsung, Huawei, NEC, CATT, ZTE, Ericsson |
| R3-250696 |
Support for OD-SIB1 mechanism at Cell A and NES Cell |
Rakuten Mobile, Inc |
| R3-250801 |
CB:#ES2 |
Ericsson |
| R3-250845 |
Xn impact of On-demand SIB1 for UEs in idle/inactive mode |
Ericsson, Deutsche Telekom, China Unicom, CMCC, Lenovo, NEC, Samsung, CATT, Huawei, Rakuten |
| R3-250912 |
(TP for BL CR for TS 38.423) Xn impact of On-demand SIB1 for Ues in idle/inactive mode |
Ericsson, Deutsche Telekom, China Unicom, CMCC, Lenovo, NEC, Samsung, CATT, Huawei, Rakuten, JIO, Qualcomm Inc, ZTE, Nokia |
| 17.4 |
Others |
|
| R3-250024 |
LS on energy saving indication from CN to RAN |
SA2(Ericsson) |
| R3-250387 |
Reply LS on energy saving indication from CN to RAN |
Ericsson Telecomunicazioni SpA |
| R3-250535 |
Energy saving indicator from AMF and adaptation of common signals/channels |
Nokia |
| R3-250552 |
Adaptation of common signal/channel transmissions |
Ericsson |
| R3-250586 |
Discussion on energy saving indication from CN to RAN |
Huawei, CATT, NEC |
| R3-250587 |
[draft] Reply LS on energy saving indication from CN to RAN |
Huawei, CATT, NEC |
| R3-250812 |
Reply LS on energy saving indication from CN to RAN |
RAN3(Huawei) |
| 18.1 |
General |
|
| R3-250930 |
(BL CR to 38.413) Introduction of low-power wake-up signal and receiver for NR |
ZTE Corporation, Nokia, Samsung, Ericsson, Huawei, CATT, NTTDoCoMo |
| 18.2 |
Support LP-WUS Indicating Paging Monitoring |
|
| R3-250021 |
LS Reply on LP-WUS subgrouping |
SA2(Huawei) |
| R3-250091 |
Conclusions on RAN3 Impacts of LP-WUS |
Nokia |
| R3-250092 |
Support of LP-WUS |
Nokia |
| R3-250105 |
Support LP-WUS subgrouping in RRC_IDLE/RRC_INACTIVE |
Qualcomm Inc. |
| R3-250126 |
(TP for TS 38.413 and TS 38.423) Discussion on Low-power wake-up signal and receiver for NR |
Huawei |
| R3-250127 |
Introduction of low-power wake-up signal and receiver for NR |
Huawei |
| R3-250128 |
[draft] Reply LS on LP-WUS subgrouping |
Huawei |
| R3-250166 |
Discussion on UE Identity Index Value for LP-WUS subgroup |
NEC |
| R3-250186 |
Discussion on remaining issues for LP-WUS |
ZTE Corporation |
| R3-250187 |
(TP to TS 38.413, 38.473, 38.423) on support of LP-WUS |
ZTE Corporation |
| R3-250296 |
Further discussion on LP-WUS |
NTT DOCOMO INC.. |
| R3-250368 |
Discussion on LP-WUS for NR and LS from SA2 |
vivo |
| R3-250369 |
BLCR for TS 38.300 on support of LP-WUS |
vivo, NTT DOCOMO INC. |
| R3-250473 |
Introduction of LP-WUS paging monitoring |
Ericsson |
| R3-250487 |
Support of Low power radio WUS |
Ericsson |
| R3-250598 |
Potential RAN3 impacts of LP-WUS |
CATT |
| R3-250599 |
[Draft] Reply to LS on LP-WUS subgrouping |
CATT |
| R3-250667 |
Discussion on supporting LP-WUS Indicating Paging Monitoring |
CMCC |
| R3-250829 |
CB:#LPWUS |
NTT DOCOMO INC. |
| R3-250838 |
Introduction of low-power wake-up signal and receiver for NR |
Nokia |
| R3-250839 |
Introduction of low-power wake-up signal and receiver for NR |
Huawei, Nokia, Samsung, Ericsson, CATT, ZTE, Vivo, NTT DOCOMO INC. |
| R3-250840 |
(TP to TS 38.413) Introduction of low-power wake-up signal and receiver for NR |
ZTE Corporation, Nokia, Samsung, Ericsson, Huawei, CATT, NTT |
| R3-250841 |
Introduction of low-power wake-up signal and receiver for NR |
vivo, NTT DOCOMO INC. |
| R3-250842 |
Introduction of low-power wake-up signal and receiver for NR |
Ericsson |
| R3-250913 |
Introduction of low-power wake-up signal and receiver for NR |
Ericsson |
| 19.2 |
Support CLI Handling |
|
| R3-250163 |
Discussion on CLI handling support |
NEC |
| R3-250193 |
Signaling design to enable NR SBFD operation |
Qualcomm Incorporated |
| R3-250194 |
CLI Mitigation |
Charter Communications, Inc |
| R3-250329 |
Discussion on Evolution of Duplex Operation |
CATT |
| R3-250330 |
(TP for 38.420, 38.423, 37.340 and 38.473) Support SBFD Operation |
CATT |
| R3-250382 |
Discussion on issues of CLI handling in SBFD |
LG Electronics Inc. |
| R3-250431 |
Discussion on Information exchange for SBFD |
ZTE corporation |
| R3-250432 |
(TP for BLCR 38.300&401&420&423&473) SBFD |
ZTE corporation |
| R3-250469 |
Discussion on RAN3 impacts to support enhancements for CLI handling for SBFD |
Ericsson |
| R3-250470 |
TP to TS38.423 on enhancements for CLI handling for SBFD |
Ericsson |
| R3-250537 |
Further discussion on network support for SBFD operation and CLI management |
Nokia |
| R3-250622 |
Discussion on information exchanges among gNBs for CLI handling |
Samsung |
| R3-250623 |
TPs to BLCRs of TS38.423 and TS38.473 on CLI handling |
Samsung |
| R3-250651 |
Further discussions on SBFD related information exchange |
Huawei, China Telecom,China Unicom |
| R3-250652 |
Stage 2&3 CR on the introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) |
Huawei |
| R3-250653 |
Stage 2&3 CR on the introduction of Evolution of NR duplex operation: Sub-band full duplex (SBFD) |
Huawei |
| R3-250662 |
Discussion on supporting CLI handling in SBFD |
CMCC |
| R3-250663 |
(TP for TS 38.423) Support CLI handling |
CMCC |
| R3-250803 |
CB:#SBFD |
Huawei |
| R3-250843 |
LS on SBFD information exchange among gNBs for CLI mitigation |
RAN3(Huawei) |
| R3-250888 |
SBFD information exchange among gNBs for CLI mitigation |
RAN3(Huawei) |
| 20.1 |
General |
|
| R3-250019 |
Reply LS on AIML data collection |
SA2(Interdigital) |
| R3-250028 |
Reply LS on AIML Data Collection |
SA5(Nokia) |
| R3-250031 |
Reply LS on AIML Data Collection |
SA5(Samsung) |
| R3-250488 |
Work Plan for Rel-19 on AI/ML for PHY (Positioning) |
Rapporteur (Ericsson) |
| 20.2 |
Support Positioning Accuracy Enhancements |
|
| R3-250068 |
LS on LMF-based AI/ML Positioning for Case 2b |
SA2(VIVO) |
| R3-250074 |
LS on LMF-based AI/ML Positioning for case 3b |
SA2(Ericsson) |
| R3-250085 |
Discussion on support of AIML based positioning accuracy enhancement |
Baicells |
| R3-250113 |
(TP to BL CR for TS38.455) Support of LMF-based AI positioning |
CATT |
| R3-250114 |
(TP to BL CRs) Support of gNB-based AI positioning |
CATT |
| R3-250145 |
[Draft LS] Reply LS to SA2 on LMF-based AI/ML Positioning for case 3b |
ZTE Corporation |
| R3-250146 |
[TP to 38.455 & 38.473 & 38.401] Support of AI/ML assisted Positioning (case 3a & 3b) |
ZTE Corporation |
| R3-250155 |
(TP for TS 38.455) Support of gNB-side model (case 3a) |
Xiaomi |
| R3-250156 |
(TP for TS 38.455) Support of LMF-side model (case 3b) |
Xiaomi |
| R3-250179 |
Discussion on AI/ML based Positioning Accuracy Enhancements |
NEC |
| R3-250291 |
AIML for gNB assisted positioning |
Lenovo |
| R3-250345 |
Discussion on support of direct AI/ML positioning (Case 3b) |
China Telecom |
| R3-250346 |
Discussion on support of AI/ML assisted positioning (Case 3a) |
China Telecom |
| R3-250378 |
(TP for AI/ML BLCR to TS 38.455 for Case 3a and TP for AI/ML BLCR to TS 38.455 for Case 3b) Discussion on RAN3 impacts for AI/ML positioning |
Huawei |
| R3-250379 |
([Draft] Reply LS to SA2) Discussion on LS from SA2 on LMF-based AI/ML Positioning for Case 3b |
Huawei |
| R3-250388 |
Discussion on AI/ML-based Positioning Accuracy Enhancements |
CEWiT, Tejas Networks |
| R3-250413 |
Draft Response LS on LMF-based AI/ML Positioning for Case 3b |
Qualcomm Incorporated |
| R3-250414 |
AI/ML based positioning accuracy enhancements |
Qualcomm Incorporated |
| R3-250489 |
[draft] Reply LS on LMF-based AI/ML Positioning for case 3b |
Ericsson |
| R3-250490 |
Discussion on NRPPa signalling design for AI/ML for PHY |
Ericsson |
| R3-250491 |
CRs set to NRPPa/NGAP/F1AP BL CRs for AI/ML for PHY |
Ericsson |
| R3-250514 |
(TP to BL CR for TS 38.455) Support Direct AI ML Positioning |
CMCC |
| R3-250515 |
Support Assisted AI ML Positioning |
CMCC |
| R3-250562 |
AI/ML-based Positioning |
Jio Platforms (JPL) |
| R3-250578 |
(TP to TS 38.300,TS 38.305,TS 38.455) AI/ML Positioning Case 3a |
Nokia |
| R3-250579 |
[Draft] Reply LS on LMF-based AI/ML Positioning for case 3b |
Nokia |
| R3-250624 |
Discussion on Case 3a in AI/ML for positioning |
Samsung |
| R3-250625 |
Discussion on Case 3b in AI/ML for positioning |
Samsung |
| R3-250796 |
Reply LS on LMF-based AI/ML Positioning for case 3b |
RAN3(ZTE) |
| R3-250873 |
Summary of Offline Discussion for CB # AIPHY |
Nokia |
| 22.1 |
General |
|
| R3-250206 |
Work plan for NR sidelink multi-hop relay |
LG Electronics, InterDigital |
| R3-250939 |
(BL CR to 38.401) Support of Multi-hop relay |
LG Electronics Inc., ZTE, Nokia, Nokia Shanghai Bell, Ericsson, FirstNet, Huawei |
| R3-250940 |
(BL CR to 38.413) Support of Multi-hop relay |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, LG Electronics, NEC, CATT, InterDigital, Samsung, ZTE, FirstNet, NIST |
| R3-250941 |
(BL CR to 38.423) Support of Multi-hop relay |
Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, Huawei, NEC, CATT, InterDigital, Samsung, ZTE, FirstNet, NIST |
| R3-250942 |
(BL CR to 38.473) Support of Multi-hop relay |
Huawei, LG Electronics, Nokia, Nokia Shanghai Bell, NEC, CATT, Ericsson, Samsung, ZTE, Interdigital, FirstNet |
| 22.2 |
Support multi-hop Layer-2 UE-to-Network relay |
|
| R3-250070 |
LS on Authorization information for Layer-2 multi-hop U2N relaying to NG-RAN |
SA2(LGE) |
| R3-250101 |
Support for Multi-hop L2 U2N relays |
Qualcomm Incorporated |
| R3-250164 |
Discussion for U2N multi-hop relay |
NEC |
| R3-250188 |
Discussion on support of multi-hop SL relay |
ZTE Corporation |
| R3-250189 |
(TP to TS 38.401, 38.470) on support of multi-hop SL relay |
ZTE Corporation |
| R3-250207 |
(TP for TS 38.401) Support of Multi-hop relay |
LG Electronics |
| R3-250208 |
Discussion on service continuity in Multi-hop relay |
LG Electronics |
| R3-250225 |
Discussion on the support of multi-hop Layer-2 UE-to-Network relay |
Nokia, Nokia Shanghai Bell |
| R3-250226 |
(TP for TS 38.413) Support of multi-hop Layer-2/3 UE-to-Network relay |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, LG Electronics, NEC, CATT, InterDigital, Samsung, ZTE |
| R3-250255 |
Authorization for multi-hop relay |
Huawei |
| R3-250256 |
(TP for BLCR 38.473) Authorization for multi-hop relay |
Huawei, LG Electronics, Nokia, Nokia Shanghai Bell, NEC, CATT, Ericsson, Samsung, ZTE |
| R3-250257 |
Support of multi-hop relay |
Huawei |
| R3-250331 |
Discussion on multi-hop Layer-2 UE-to-Network relay |
CATT |
| R3-250353 |
UE authorization for multi-hop relay |
China Telecom |
| R3-250354 |
Discussion on control plane procedures for multi-hop relay |
China Telecom |
| R3-250526 |
(TP for TS 38.423) – Authorization info for SL Multi-hop Relay |
Ericsson, LG Electronics, Nokia, Nokia Shanghai Bell, Huawei, NEC, CATT, InterDigital, Samsung, ZTE |
| R3-250527 |
Authorization of Intermediate Relay UEs in RRC_INACTIVE |
Ericsson |
| R3-250528 |
QoS handling for Multi-hop Relay |
Ericsson |
| R3-250638 |
Discussion on multi-hop for SL relay |
Samsung |
| R3-250837 |
CB:#Multihop_SAidelinkRelay |
LGE |
| R3-250878 |
(TP for TS 38.401) Support of Multi-hop relay |
LG Electronics Inc., ZTE, Nokia, Nokia Shanghai Bell, Ericsson, FirstNet |
| 31.1 |
Corrections |
|
| R3-250061 |
Inactivity Timer for Fixed Wireless Access |
Nokia, Ericsson, Huawei, ZTE |
| R3-250083 |
Inactivity Timer for Fixed Wireless Access |
Huawei, Nokia, ZTE, Ericsson |
| R3-250190 |
Discussion on X2/Xn exchange of signalling TNL addresses for signalling transport establishment |
Ericsson, Vodafone, Huawei |
| R3-250228 |
X2 TNL address exchange |
Vodafone, Ericsson, Huawei |
| R3-250229 |
Xn TNL address exchange |
Vodafone, Ericsson, Huawei |
| R3-250230 |
X2 TNL address exchange |
Vodafone, Ericsson, Huawei |
| R3-250231 |
Xn TNL address exchange |
Vodafone, Ericsson, Huawei |
| R3-250262 |
(TP for XR BL CR for TS37.340) Support for ECN marking status change |
Huawei, CMCC, CATT, Nokia, Nokia Shanghai Bell, BT, Vodafone |
| R3-250747 |
Response to R3-250190 |
ZTE Corporation |
| R3-250752 |
Response to R3-250190 |
Huawei |
| R3-250782 |
Inactivity Timer for Fixed Wireless Access [Inactivity_Timer_FWA] |
Nokia, Ericsson, Huawei, ZTE |
| R3-250783 |
Inactivity Timer for Fixed Wireless Access [Inactivity_Timer_FWA] |
Huawei, Nokia, ZTE, Ericsson |
| R3-250784 |
CB:#9_TNLAddress |
Vodafone |
| 31.2 |
Enhancements |
|
| R3-250093 |
Introduction of SDT network-based solution |
Nokia, Ericsson, Huawei, LG Electronics, CATT |
| R3-250094 |
Response LS on SDT signalling optimization for partial context transfer |
Nokia, Ericsson, Huawei, LG Electronics, CATT |
| R3-250112 |
Introduction of SDT network-based solution [SDT-NW-sol] |
CATT, Huawei, Nokia, Ericsson, LG Electronics |
| R3-250125 |
Introduction of SDT network-based solution [SDT-NW-sol] |
LG Electronics, Nokia, Ericsson, Huawei, CATT |
| R3-250157 |
Introduction of SDT network-based solution [SDT-NW-sol] |
Ericsson, Nokia, Huawei, LG Electronics, CATT |
| R3-250159 |
Introduction of SDT network-based solution [SDT-NW-sol] |
Huawei, Nokia, Ericsson, LG Electronics, CATT |
| R3-250203 |
NR to LTE mobility restriction |
NTT DOCOMO INC., Nokia |
| R3-250363 |
Discussion on the impact of cell DTXDRX |
CATT, ZTE, NEC |
| R3-250364 |
(draft CR to 38.423) Rel-18 Support Cell DTXDRX for NES |
CATT, ZTE, NEC, Huawei |
| R3-250395 |
Enhancements for Data Collection Reporting |
Ericsson Telecomunicazioni SpA |
| R3-250428 |
Introduction of cell DTX/DRX information |
Ericsson, Nokia |
| R3-250492 |
Discussion on improving E-CID positioning accuracy |
Ericsson, NTT DOCOMO, Nokia, Polaris Wireless, ZTE, CATT |
| R3-250493 |
E-CID measurement enhancement [E-CID-enh1] |
Ericsson, NTT Docomo, Nokia, Polaris Wireless, ZTE, CATT |
| R3-250494 |
E-CID measurement enhancement [E-CID-enh1] |
Ericsson, NTT Docomo, Nokia, Polaris Wireless, ZTE, CATT |
| R3-250495 |
Indication of new cell ID for E-CID positioning [E-CID-enh2] |
Ericsson, CATT, ZTE, Polaris Wireless, NTT Docomo, Xiaomi |
| R3-250536 |
Introduction of cell DTX/DRX information |
Nokia, Ericsson |
| R3-250567 |
Enhancement of mobility restriction [Enhanced Mobility] |
Nokia |
| R3-250704 |
Enhancing QoS Monitoring with Per-Packet Granularity |
ZTE Corporation, China Telecom, China Unicom |
| R3-250705 |
Correction to enhancing QoS Monitoring with Per-Packet Granularity |
ZTE Corporation, China Telecom, China Unicom |
| R3-250749 |
Response document to R3-250093 |
Qualcomm Incorporated, ZTE |
| R3-250750 |
Response to R3-250093 |
ZTE Corporation |
| R3-250753 |
Response to R3-250203 and R3-250567 |
Huawei |
| R3-250849 |
CB:#30_DTXDRX |
CATT |
| R3-250852 |
CB:#31_QoSmonitoring |
ZTE |
| 32 |
Any other business |
|
| R3-250757 |
RAN3 Basketball Introduction |
ZTE |